[gs-bugs] [Bug 690025] New: pxlmono driver prints some glyphs as squares when the input is PostScript generated by Ghostscript

[bugs.ghostscript.com-bugzilla-daemon at ghostscript.com]

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

           Summary: pxlmono driver prints some glyphs as squares when the
                    input is PostScript generated by Ghostscript
           Product: Ghostscript
           Version: 8.63
          Platform: PC
               URL: http://bugs.linux-foundation.org/show_bug.cgi?id=158
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: P4
         Component: Printer Driver
        AssignedTo: support at artifex.com
        ReportedBy: till.kamppeter at gmail.com
         QAContact: gs-bugs at ghostscript.com


See

http://bugs.linux-foundation.org/show_bug.cgi?id=158

The bug occurs on integration of legacy drivers into the PDF printing workflow
(PDF as standard print job format):

A driver (here "pxlmono") has options which are based on PostScript code to be
embedded in the incoming PostScript data stream. This means that the driver
cannot be controlled when Ghostscript is fed with PDF. These cases are
auto-detected by foomatic-rip and fommatic-rip does the following then:

PDF --Ghostscript-> PS --embed options-> PS --Ghostscript-> PCL-XL

The PostScript which the first Ghostscript process produces (with output device
"pswrite") leads the second Ghostscript process to loose characters and print
them as squares when converting to PCL-XL with "pxlmono".

See the scanned printout in the above-mentioned bug report. See also sample
files there.

Or do

gs -q -sstdout=%stderr -sDEVICE=pswrite -sOutputFile=- -dBATCH -dNOPAUSE
-dPARANOIDSAFER /home/till/walking-map-portland-1.pdf > test.ps
gs -q -sstdout=%stderr -sDEVICE=pxlmono -sOutputFile=- -dBATCH -dNOPAUSE
-dPARANOIDSAFER test.ps > test.pxl

and send the text.pxl unfiltered to a PCL-XL printer.



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