(In reply to comment #6)
> Generally, I can make Foomatic selecting ljet4 when the user unselects
> duplex and ljet4d when he selects duplex, but problem is if GS gets fed with
> PostScript files containing Duplex and Tumble settings. Then the standard
> control via the Duplex and Tumble parameters in needed to get correct
> results.
Okay so we'll look into changing ljet4d to only duplex if the options are sent.
I'm hesitant to have one device ljet4 that supports duplexing - I have to think there is a reason ljet4d exists, and a possible explanation is sending PCL duplex commands to some non duplexing printer results in an error. I wish we had better history about why ljet4d was created in the first place.
(In reply to comment #6)
> Generally, I can make Foomatic selecting ljet4 when the user unselects
> duplex and ljet4d when he selects duplex, but problem is if GS gets fed with
> PostScript files containing Duplex and Tumble settings. Then the standard
> control via the Duplex and Tumble parameters in needed to get correct
> results.
Okay so we'll look into changing ljet4d to only duplex if the options are sent.
I'm hesitant to have one device ljet4 that supports duplexing - I have to think there is a reason ljet4d exists, and a possible explanation is sending PCL duplex commands to some non duplexing printer results in an error. I wish we had better history about why ljet4d was created in the first place.