Update of bug #67295 (group groff):
Assigned to: deri => gbranden
_______________________________________________________
Follow-up Comment #4:
I notice that gropdf does emit a warning:-
gropdf: warning: Unable to parse font 'Symbol-Slanted' for subsetting
The perl messages can be turned off if you think that is a good idea. I
wondered what grops would do if I "hand edited" freeeuro.pfa (deleted a single
character).
[derij@pip devps (master)]$ echo "\(Eu\(eu"|test-groff | okular -
(libspectre) ghostscript reports: undefined -21
(libspectre) ghostscript reports: undefined -21
(libspectre) ghostscript reports: undefined -21
(libspectre) ghostscript reports: undefined -21
It appears grops did not recognise it was an invalid font at all, just stuffed
it in the output, giving okular/ghostscript some indigestion, so 1 up for
gropdf. :-)
I think we have have to accept that if your font is not valid, you will
receive unusual errors. To fully validate a type 1 font would take an awful
lot of code for both grops and gropdf.
However, I think gropdf could do better, at least look for a valid font
header, and if what appears after it is invalid, rely on the message above
that gropdf can't use it. At least gropdf tells them which font is causing the
issue, unlike grops/okular.
I will commit a suitable change.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67295>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
