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 output, so that is where the problem is now > (although it looks like PSOutputDev in xpdf's source that isn't built > anymore should also have the issue). I don't have a printer to test, > but I've attached a potential solution. Would you be able to test it? > Note that this needs to be applied to poppler. Thanks for looking into this. I would be happy to test this. I'll get back to you at some point. But: --- poppler/PSOutputDev.cc.orig 2011-08-18 02:35:01.000000000 -0400 +++ poppler/PSOutputDev.cc 2011-08-18 02:35:22.000000000 -0400 @@ -117,7 +117,7 @@ " /PageSize exch def", " /ImagingBBox null def", " /Policies 1 dict dup begin /PageSize 3 def end def", - " { /Duplex true def } if", + " { /Duplex false def } if", " currentdict end setpagedevice", " } {", " pop pop", I don't think this is right. If I have configured my printer to do duplex, this would force it to simplex for this document. The correct behaviour is simply not to mess with this at all. I can see no reason for anything generating PS output to do so, and frankly I think it's mind-boggling that this code is in Poppler at all. The right patch is probably this: " /PageSize exch def", " /ImagingBBox null def", " /Policies 1 dict dup begin /PageSize 3 def end def", - " { /Duplex true def } if", " currentdict end setpagedevice", " } {", And that is what I plan to test. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org