|
|
>> When allowing, how to prevent creating buggy PDFs ? There is no solution *at all*. The worst in the case is that file ripping can succeed, but the result will obviously not be correct. [Edit] in a decent PDF processing workflow, this kind of file will be rejected and will never reach the press. Return to the page layout guy => time lost. |
|
|
>> But, when user changes the font of a text, scribus doesnt check that all used glyphs exist in the new font and *does* allow to create a non existing glyph. An empty square is displayed. >> It seems importing text also imports non existing glyphs. For those cases the preflight verifier already checks for non existing glyphs. >> When not allowing how to deal with the requests to create one ? How to notify the error and not silently fail ? An acceptable solution would be creating some kind of bubble hint. Inserting the missing glyph is not. |
|
|
would it be hard to do as firefox does and show a box with a code in it? cf. attachment. |
|
|
char-codes.jpg (6,360 bytes) |
- Anonymous
