autoduplex constraints should be dropped
Bug #487695 reported by
Tim Waugh
This bug affects 18 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Common Print Dialog |
New
|
Wishlist
|
Unassigned | ||
HPLIP |
New
|
Undecided
|
Unassigned | ||
hplip (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Maverick |
Fix Released
|
Undecided
|
Unassigned | ||
Natty |
Fix Released
|
Undecided
|
Unassigned | ||
system-config-printer (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Maverick |
Fix Released
|
Undecided
|
Unassigned | ||
Natty |
Invalid
|
Undecided
|
Unassigned |
Bug Description
The "autoduplex" page sizes are a clever way of allowing the application to know in advance exactly where the page margins are when duplexing. However, it should not be an actual constraint on whether duplexing can be enabled.
The reason is that it can never be clear to the user why they cannot select a duplexing option. Their page size setting is correct (e.g. A4), and the installable options setting says that a duplexer is installed. There is no way to discover the "magic" page sizes.
Also there is no way for CUPS to know to set this magic page size as the default when adding a queue. It will look for "A4" or "Letter" depending on the locale.
Changed in system-config-printer (Ubuntu Natty): | |
status: | New → Invalid |
To post a comment you must log in.
When the user has selected the page size "A4",
all other page size entries in the PPD are
meaningless.
When the user has selected the page size "A4"
plus "duplex printing", the ImageableArea is still
those for "A4".
When the the ImageableArea for "A4" does not work
for "duplex printing", there must be matching
UIConstraints in the PPD to exclude both mutually.
Have a look at /bugs.launchpad .net/evince/ +bug/428588/ comments/ 22 /bugs.launchpad .net/hplip/ +bug/237342
https:/
and
https:/
On the one hand:
Whenever some kind of settings cannot work together,
appropriate UIConstraints must be specified in the PPD
so that the user's printing interface can show impossible
settings before a wrong or unexpected printout happens.
But on the other hand:
The defaults in a PPD must be so that all UIConstraints
are fulfilled so that by default printing "just works".