Hi, Am Sonntag, den 15.02.2009, 18:37 +0100 schrieb a...@librelogiciel.com: > On Sun, Feb 15, 2009 at 03:05:04PM +0100, Joachim Breitner wrote: > > > > I’m not sure if I can follow this argument. The attached print file was > > not valid postscript, but rather postscript wrapped in an PJL print job, > > if I understand it correctly. Therefore, it can not be a bug in > > ghostscript. > > You may be correct. > > However, simply take pykota and pkpgcounter out of the equation, and > use instead the cups-pdf backend for CUPS, written by Volker C. Behr. > > I bet you'll have the very same problem (untested, but from reading its > source code it launches gs and doesn't strip out any PJL).
Hmm. I’d assume that for cups-pdf, you would not use the .ppd file for a real printer model (a kyocera printer in my case), so cups would not add the PJL header, and send the plain PS. At least I assume so, as otherwise cups-pdf would not work :-) > This means this bug should be reported to any similar software, > duplicating efforts needlessly. > > Really it depends if we consider gs is emulating a printer or is only a > PS interpreter. In the first case it should recognize PJL's Universal > Exit Language (<ESC>%-12345X) because the document, as seen from a > printer supporting PJL and PostScript, is perfectly correct. In the > latter case it doesn't need to. > > Not sure what GhostScript developers think about this problem. > > I'm not 100% against implementing a workaround for this problem, but > I'd prefer that ghostscript developers handle this situation, > otherwise other developers would have to create similar workarounds > for their own software. I’d expect them so see the latter case (PS interpreter), but from a user point of view, it doesn’t matter much :-) Thanks, Joachim -- Joachim "nomeata" Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
