URL:
<http://savannah.gnu.org/bugs/?46327>
Summary: groff should fail rather than producing invalid
PostScript code
Project: GNU troff
Submitted by: barx
Submitted on: Thu 29 Oct 2015 05:07:10 PM CDT
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release: None
_______________________________________________________
Details:
If a problem prevents groff from generating valid PostScript output, groff
should fail with an error message and a failure exit status, rather than
exiting successfully and producing erroneous PostScript.
For instance, my system had a misconfigured
/usr/share/groff/site-font/devps/download file, with an entry that pointed to
the font description file rather than the intended .pfa file. I ran groff on
a document that used this misconfigured font, and groff exited successfully
and produced a PostScript file. However, that PostScript file caused gv to
throw an "Error: /undefined in #" and stack trace.
To reproduce this, create font description file
/usr/share/groff/site-font/devps/TRSC containing the line "internalname
Times-RomanSC", and add the following entry to the downloads file:
$ echo -e "Times-RomanSC\tTRSC" >> /usr/share/groff/site-font/devps/download
Then try to use this font in a simple groff document:
$ groff > test.ps << EOF
.fp 5 RSC TRSC
.ft 5
Hi.
EOF
$ echo $?
This runs with no errors and exits with a successful status. But the
resultant test.ps is not valid PostScript.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?46327>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
bug-groff mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-groff
