OpenPrinting / OpenPrinting/libppd
When printing with driverless, the “print-content-optimize” setting does not work
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 5
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
When printing with driverless, the “print-content-optimize” setting does not work
To Reproduce
Steps to reproduce the behavior:
- Add a printer "fooA" in the legacy-printer-app
- Add a driverless for the "fooA"
- Open any document by evnice and print the doucment with the "print-content-optimize" = "text"
- PAPPL cannot receive the "print-content-optimize" value.
Expected behavior
PAPPL can receive the value of "print-content-optimize".
System Information:
- OS: [Ubuntu24.04]
- Version of CUPS, libcupsfilters, ...
CUPS: 2.4.7
libcupsfilters: 2.0.0
PAPPL: 1.4.9
Additional context
- The "print-content-optimize" option generated by driverless is as follows
*OpenUI *print-content-optimize/Print Optimization: PickOne
*OrderDependency: 10 AnySetup *print-content-optimize
*Defaultprint-content-optimize: auto
*print-content-optimize auto/Automatic: ""
*print-content-optimize graphic/Graphics: ""
*print-content-optimize photo/Photo: ""
*print-content-optimize text-and-graphic/Text and Graphics: ""
*print-content-optimize text/Text: ""
*CloseUI: *print-content-optimize
- Everywhere does not generate the "print-content-optimize" option.
- "print-content-optimize" setting is filtered out when printing via ipp-backend.https://github.com/OpenPrinting/cups/blob/c83115cc35d6ec865a405260f0c61d372804be4e/cups/ppd-cache.c#L145
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect cups/ppd-cache.c around line 145 and trace how the driverless PPD option reaches the ipp-backend. Reproduce the print-content-optimize=text case from the issue, then verify that PAPPL receives the selected value without filtering it out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100