[gs-bugs] [Bug 692691] New: Inserting PostScript commands from options in PPD files into "ps2write"-generated PostScript does not have any effect

[bugzilla-daemon at ghostscript.com]

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

           Summary: Inserting PostScript commands from options in PPD
                    files into "ps2write"-generated PostScript does not
                    have any effect
           Product: Ghostscript
           Version: 9.04
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P4
         Component: PS Writer
        AssignedTo: ken.sharp at artifex.com
        ReportedBy: till.kamppeter at gmail.com
         QAContact: gs-bugs at ghostscript.com


Created an attachment (id=8130)
 --> (http://bugs.ghostscript.com/attachment.cgi?id=8130)
printout-lp885118.pdf

In the CUPS filtering workflow in Ubuntu Oneiric I use Ghostscript with the
"ps2write" output device to convert PDF into PostScript, for PostScript
printers and legacy drivers which require PostScript as input.

Problem is that if the PPD file executes option settings by inserting
PostScript code snippets, the common way for PostScript printer PPDs, the code
seems not to get respected.

An example is the attached PostScript file. "ps2write" generated it from the
attached PDF file and afterwards

[{
%%BeginFeature: *Duplex DuplexNoTumble
<</Duplex true /Tumble false>>setpagedevice
%%EndFeature
} stopped cleartomark

got inserted into the "%%BeginSetup ... %%EndSetup" section. It does not matter
where in the section these lines get inserted, the problem always occurs. I
tried different places.

When trying to print this file unfiltered on a PostScript printer (HP Color
LaserJet CM3530 MFP in my case) the two pages come out on separate sheet and
not on the front and back of one sheet.

I am using Ghostscript 9.04 on Ubuntu Oneiric (11.10). This causes especially
the following Ubuntu bug:

https://bugs.launchpad.net/ubuntu/+source/cups/+bug/885118

To reproduce:

Convert the attached PDF file into PostScript via

pdf2ps printout-lp885118.pdf

Then edit the resulting PostScript file adding the lines

%%BeginSetup
[{
%%BeginFeature: *Duplex DuplexNoTumble
<</Duplex true /Tumble false>>setpagedevice
%%EndFeature
} stopped cleartomark
%%EndSetup

right after the line "%%EndProlog".

The lines are what gets inserted if the PPD contains

*OpenUI *Duplex/Double-Sided Printing: PickOne
*OrderDependency: 130 AnySetup *Duplex
*DefaultDuplex: None
*Duplex DuplexNoTumble/Long Edge (Standard): "<</Duplex true /Tumble
false>>setpagedevice"
*Duplex DuplexTumble/Short Edge (Flip): "<</Duplex true /Tumble
true>>setpagedevice"
*Duplex None/Off: "<</Duplex false>>setpagedevice"
*CloseUI: *Duplex

and the job is sent with the option setting "Duplex=DuplexNoTumble".

This file is supposed to come out double-sided on a PostScript printer with
Duplex unit. What happens is that it comes out single-sided on two sheets.

Alternatively to editing the PostScript file you can also apply the option
setting by running it through the appropriate CUPS filter:

PPD=ML-2850-Series.ppd /usr/lib/cups/filter/pstops 1 1 1 1
"Duplex=DuplexNoTumble" printout-lp885118.ps > printout-lp885118-duplex.ps

-- 
Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.