[gs-bugs] [Bug 690291] Handling of the PJL's Universal Exit Language sequence

bugs.ghostscript.com-bugzilla-daemon at ghostscript.com bugs.ghostscript.com-bugzilla-daemon at ghostscript.com
Thu Feb 19 08:21:45 PST 2009


http://bugs.ghostscript.com/show_bug.cgi?id=690291

ray.johnston at artifex.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From ray.johnston at artifex.com  2009-02-19 08:21 -------
I consider this file as invalid PostScript. The data sequence beginning with
!R!CRES... is not valid PostScript, nor is it a PJL command.

Alex's suggestion in comment #4 won't work since PJL can have spaces between
tokens.

I think this is a case where the file should be fixed by pre-filtering to remove
the non-PS data sequence before the valid PS. This can be done with perl, sed or
awk, but I am against adding some kind of partial solution to Ghostscript that
might break other files that have PJL headers.

Of course, since full source is provided an individual is welcome to modify
their local copy to do as Alex suggests.



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.



More information about the gs-bugs mailing list