Michael Gilbert writes ("Bug#617546: xpdf prints duplex, overriding printer
front panel"):
> Agreed. I'm not that familiar with postscript duplexing, so that was
> just my best guess.
Actually, rereading my proposal, it's clearly wrong. I know enough
PostScript to f
On Thu, Aug 18, 2011 at 7:58 AM, Ian Jackson wrote:
> --- poppler/PSOutputDev.cc.orig 2011-08-18 02:35:01.0 -0400
> +++ poppler/PSOutputDev.cc 2011-08-18 02:35:22.0 -0400
> @@ -117,7 +117,7 @@
> " /PageSize exch def",
> " /ImagingBBox null def",
> "
retitle 617546 popper: PSOutputDev should not mess with duplex setting
thanks
Michael Gilbert writes ("Bug#617546: xpdf prints duplex, overriding printer
front panel"):
> I just had a couple minutes to look into this. xpdf now uses poppler's
> PSOutputDev for postscript out
reassign 617546 poppler
retitle 617546 popper: PSOutputDev should produce simplex output by default
tag 617546 patch
thanks
I just had a couple minutes to look into this. xpdf now uses poppler's
PSOutputDev for postscript output, so that is where the problem is now
(although it looks like PSOutpu
This is still a problem in 3.02-21 (and I agree that xpdf should
not be setting Duplex mode). Until it's fixed, one workaround is
to change the psFile definition in /etc/xpdf/xpdfrc to something
like:
psFile "|sed 's/ true pdfSetup/ false pdfSetup/' | lpr"
Bill
--
To UNSUBSCRIBE, e
Package: xpdf
Version: 3.02-12
To reproduce:
xpdf test.pdf (file attached)
ask xpdf to print to file test.ps
Observe in the generated output:
/pdfSetup {
3 1 roll 2 array astore
/setpagedevice where {
pop 3 dict begin
/PageSize exch def
/ImagingBB
6 matches
Mail list logo
