Bug 33547 - LPR/LPRng for kprinter:duplex printing not supported
Summary: LPR/LPRng for kprinter:duplex printing not supported
Status: CLOSED INTENTIONAL
Alias: None
Product: kdeprint
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: KDEPrint Devel Mailinglist
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 19:33 UTC by klee
Modified: 2008-12-31 12:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
sample filter for postscript duplex printing (107 bytes, text/x-sed)
2004-08-10 17:52 UTC, mi+kde
Details

Note You need to log in before you can comment on or make changes to this bug.
Description klee 2001-10-10 19:20:30 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           kdeprint
Version:           unknown (using KDE 2.2.1 )
Severity:          wishlist
Installed from:    compiled sources
Compiler:          gcc version 2.95.3 20010315 (release)
OS:                Linux (i686) release 2.4.7-UP
OS/Compiler notes: 

In the old per-application printing scheme I was able to specify duplex printing (for applications such as kviewshell) by manually typing the "-Z duplex" option for lpr.  The new unified print system is nice except that there's no good way to specify duplex printing manually or otherwise.

I've created a pseudo printer that pipes through lpr with the -Z duplex option but that's inconvenient if the site has a lot of printers.  Also pseudo-printers are crippled relative to real printers: you cannot save paper size and other options for such printers and you cannot set them as the default printer.

I suggest an option for every printer (at least with lpr) that allows you to specify -Z options manually.  Perhaps common options such as "duplex" and "slide" should be available as check boxes.

(Submitted via bugs.kde.org)
(Called from KBugReport dialog)
Comment 1 Michael Goffioul 2002-03-03 00:53:17 UTC
I completely rewrote the LPR plugin and it is now able to handle print que=
ues
setup with Foomatic APSFilter and IFHP. With that you can setup your print
options in the printer properties dialog like the duplex.

Michael.
Comment 2 klee 2003-11-12 01:16:40 UTC
OK, this bug was closed a long time ago, but I am still unable to figure out how to enable duplex printing.  I can't find the place in the printer properties dialogs to set this option.

I am also unable, via Google or KDE documentation, to find any information on how to add the '-Z duplex' option to an LPRng printer.  There's information for CUPS, but our site (like many others) has still not migrated to CUPS, so that doesn't help.

IMO this is at least a usability bug, and should be reopened until there's an obvious way in the UI for the user to set duplex printing on an LPR printer.
Comment 3 mi+kde 2004-08-10 17:52:13 UTC
Created attachment 7061 [details]
sample filter for postscript duplex printing

Use as:

	.... | duplex | lpr
Comment 4 mi+kde 2004-08-10 17:54:58 UTC
Please, add the Duplex and Tumble checkboxes. The page at

	http://www.math.tamu.edu/~harold.boas/courses/math696/duplex.html

describes how to. The duplex script just submitted provides proof of concept.

Configuring separate printers for all of these options will require 4-times as many entries...
Comment 5 Kurt Pfeifle 2007-01-11 04:39:36 UTC
If you have print options not supported by the LPR/LPRng print subsystem plugin, please use the "Print through external program"-plugin.

If you are a user who has ingrained LPRng into his habits, you should be able to come up with the correct command to insert into the "Print command:" box. If you can't do that, please consult the Foomatic+LPRng documentation on www.linuxprinting.org. Foomatic allows you to use virtually every PPD option with any non-CUPS print system, including LPRng.

We are sorry, but there is no one currently (nor was there anybody in the last 4 years) who was willing to implement full LPRng support in KDEPrint. LPRng is a dying project (or dead already?), and it doesn't look anybody is going to revive it again.

I'm going to close this as WONTFIX.
Comment 6 John Layt 2008-12-31 12:03:01 UTC
Closing old Resolved status bug.
Comment 7 John Layt 2008-12-31 12:03:12 UTC
Closing old Resolved status bug.