Bug in pstops?

[Helge Blischke]

Christoph Litauer wrote:
> 
> Helge Blischke schrieb:
> > Christoph Litauer wrote:
> >
> >>Michael Sweet schrieb:
> >>
> >>>Christoph Litauer wrote:
> >>>
> >>>
> >>>>...
> >>>>Looks like Duplex is set to 1 if the ppd file specifies duplex printing
> >>>>by default. As my ppd-File contains
> >>>>
> >>>>*DefaultDuplex: DuplexNoTumble
> >>>>...
> >>>
> >>>
> >>>No, if you look further up you'll see that we use cupsMarkOptions()
> >>>to mark the job options in the PPD options, so the Duplex options will
> >>>reflect the sides/Duplex option setting by the user, not just the
> >>>defaults in the PPD file.
> >>>
> >>
> >>Sorry Michael, I overlooked that.
> >>In the meantime I analyzed the problem a little more. The extra pages
> >>are only generated if I use the Foomatic/PostScript driver for the
> >>printer. A "print to file" document with explicit one-sided printing
> >>enabled contains:
> >>
> >>%%BeginFeature: *Duplex None
> >>%% FoomaticRIPOptionSetting: Duplex=None
> >>%%EndFeature
> >>
> >>If I print this document an extra page is added.
> >>Does pstops recognize that? What can I do against it?
> >>
> >>--
> >>Regards
> >>Christoph
> >>
> >
> >
> > If you view the file with Ghostscript, does this add the extra page
> > as well?
> 
> Yes, the output contains
> 
> %%Page: 2 2
> showpage
> 
> %%Trailer
> %%Pages: 2
> 
> But as Michael stated before, the reason is that I use foomatic drivers ...
> 
> Just two more questions:
> 1.) Wouldn't it be better to run pstops _after_ foomatic-rip?
> 2.) I I switch back to the native printer ppd files, how can I force all
> windows clients to reload the printer driver?
> 

ad 1:	Though I don't know all the details about foomatic (I/we don't use
it),
	its main purpose is to convert the PostScript output of the pstops
filter
	to something the printer will know to deal with (e.g. PostScript level
1
	or some other device specific language as defined in the PPD).
	Thus, reversing the order of execution is not possible in general.

ad 2:	If the printer is a native PostScript printer (except level1, see
above),
	I'd suggest not to use the foomatic stuff but the vendor supplied PPD;
	the pstops filter (to my experience at least) works very well with
these
	(though it is wise to run the PPDs through cupstestppd and fix the
errors).
	To reload the Winxx drivers, there are two approaches:
	a) the conventional one: delete all (literally ALL) printers that use
the
	   PPDs in question (or, if you know what you are doing, delete the 
	   respective files "by hand") and then re-create all these printer
instances.
	b) (works only in NT4 and higher): write a login script that recreates
	   all the printer instances at login time.

Helge


-- 
Helge Blischke
Softwareentwicklung
SRZ Berlin | Firmengruppe besscom
http://www.srz.de
tel: +49 30 75301-360