Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EFDuplex option from EFI PPDs not handled properly #915

Closed
michaelrsweet opened this issue Sep 23, 2004 · 3 comments
Closed

EFDuplex option from EFI PPDs not handled properly #915

michaelrsweet opened this issue Sep 23, 2004 · 3 comments
Milestone

Comments

@michaelrsweet
Copy link
Collaborator

Version: 1.2-current
CUPS.org User: speter.codehost

The CUPS code that expands the "sides" option doesn't deal with all the possible values of the EFDuplex option on EFI controllers.

I have seen several sets of common values on some PPDs - they are often not consistent but CUPS should try to support all of them:

One-sided: False, None
2-sided Long Edge: LongEdge, DuplexNoTumble, Top
2-sided Short Edge: ShortEdge, DuplexTumble, Bottom

The current code in options.c seems to assume that all the different option names for the duplex option handle the same values, which is not true in practice.

EFI also has an equivalent EFDuplexing option instead of EFDuplex in some older PPDs.

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: mike

Adding support is technically feasible, however I'm not sure how many non-standard Duplex options we want to code support for.

Also, EFDuplex isn't the standard duplex option - how many PPD files does this effect, and how difficult would it be to get permission from EFI and edit those PPD files to use the correct Duplex keyword and options?

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: speter.codehost

Yeah, EFDuplex is obviously not conforming to the standard. But for some reason that's what EFI has been sticking to. This is not the only part of the spec they routinely violate either - EFMediaType among others.

However from my experience virtually all of their PPDs use these options instead of the mandated names. You may be able to secure the permission to modify them by hand, but then future PPDs won't work as well either. We have been able to modify the PPDs we bundle in our products here but it doesn't solve the larger problem.

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: mike

Fixed in Subversion repository.

The new implementation will allow us to add additional options and choices in the future as needed...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant