Setting pdftops-renderer?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- tooling
Research direction
Review the Foomatic XML configuration path and the PPD option snippet in the issue, then compare them with the cups-filters README and CUPS PPD Extensions specification. Done means determining whether either renderer option can be represented and documenting the supported configuration path or limitation.
Written by the indexing model from the issue text.
Description
I'm having issues with the default PDF to PS renderer pdftops in ptouch-driver. As explained in the cups-filters README, the pdftops-renderer print option can be set either per job with lpr -o pdftops-renderer=gs or per queue with lpadmin -o pdftops-renderer-default=gs, which makes those issues go away.
The following posting suggests that there's a way to set pdftops-renderer from PPD files as well. However, the following PPD code has no effect:
*OpenUI *pdftops-renderer: PickOne
*Defaultpdftops-renderer: gs
*pdftops-renderer gs/GhostScript: ""
*CloseUI: *pdftops-renderer
Is there a way to define pdftops-renderer or pdftops-renderer-default in a Foomatic xml file? Note that the print option doesn't add any Foomatic command-line arguments like <arg_substitution> or PostScript code like <arg_postscript>. I couldn't figure out a way to pass printer options from the CUPS PPD Extensions specfication, either. Thanks for any help!
- Dominant language
- Perl
- Stars
- 8
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from OpenPrinting/foomatic-db-engine
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
OpenPrinting/foomatic-db-engine#12 · 1 reaction ·
-
Foomatic 4.1.0?Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
All issues in OpenPrinting/foomatic-db-engine
Similar issues
-
Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
inverse-inc/packetfence#9707 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
RotherOSS/otobo#6457 · 2 comments ·
Maintainers usually reply within 1 day
-
🏭 producer platform - spam
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
openfoodfacts/openfoodfacts-server#15447 ·
Maintainers usually reply within 1 day
-
Harden argument handling in deploy-contract.shPossibly taken @Asta-wizard claimed this 1 day ago. OpenStellar Wave
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Feyisara2108/stellargive#1377 · 3 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100