[bug #46327] groff should fail rather than producing invalid PostScript code

[Werner LEMBERG]

Update of bug #46327 (project groff):

                  Status:               Need Info => Wont Fix               
             Assigned to:                    None => wl                     
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #3:

Thanks for the output file.  I fear that neither groff nor grops can help
detect such a misconfiguration.  grops follows the `%%' comment conventions to
parse font resources, as outlined in the the Adobe technote #5001, `PostScript
Language Document Structuring Conventions Specification'.  However, if a
resource file doesn't have such comments, it is simply included into the
output – the DSC conventions are optional, so *any* file might be used as a
resource since PostScript, as a programming language, can cope with arbitrary
data.

In other words, grops itself doesn't generate invalid PostScript.  Because it
doesn't contain a PS interpreter, it doesn't have the capability to validate
include files.

Note that a GhostScript guru could certainly write a small PS program that
checks whether all resources in a given directory (or directory tree) are
valid PS code; this would help check groff's PS fonts for validity. 
Unfortunately, this is beyond my capabilities.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?46327>

_______________________________________________
  Nachricht gesendet von/durch Savannah
  http://savannah.gnu.org/