[Python-apps-team] Bug#515184: pkpgcounter failes to read PJL[well, it's not PJL]-wrapped postscript
SaGS
sags5495 at hotmail.com
Wed Feb 18 15:22:11 UTC 2009
Hi all,
I’m not a Debian user, but noticed the bug filed against Ghostscript and
would like to make a comment and suggest another thing to try.
First, the sample file is *not* valid PJL+PostScript. The "!R! ... etc ...
EXIT;" part is Kyocera's Prescribe. That's where the error comes from, as GS
does not intrepret PRESCRIBE - as it does not interpret Epson's ESC/P and
others.
Second, what I would like to suggest is to consider replacing the "!R! ...
etc" with "@PJL COMMENT !R! ... etc". Then the file will be valid
PJL+PostSCript, and there won't be any problems anymore. From what I
understad from Kyocera's documentation, the "!R!" is recognized in any
context, so I expect it has the desired effect even if "cloaked" inside a
"@PJL COMMENT". Unfortunately, I don't have such a printer to check. And,
where does this "!R!..." come from in the first place? Is it from a PPD? If
yes, and my idea works, then this bug is very easy to fix by changing the
PPD, without the need for an ugly workaround in Ghostscript.
More information about the Python-apps-team
mailing list