Different format priority compared to Everywhere

Open
#90 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c
Domain
backend

Research direction

Compare the format-priority lists in libppd/ppd/ppd-generator.c, cups/cups/ppd-cache.c, and cups-browsed/daemon/cups-browsed.c, starting at the referenced lines. Trace how driverless-generated PPDs handle cupsFilter2 and cupsUrfSupported, then determine the unified ordering and verify that all three paths use it consistently.

Written by the indexing model from the issue text.

Description

Describe the bug

As found in ticket https://github.com/OpenPrinting/libcupsfilters/issues/257, driverless, everywhere and cups-browsed all have format lists and not synced together.

Everywhere has JPEG, PNG, PDF (0/10), URF (100), PWG (100)
Driverless has PDF (0/0), URF (0), PWG (0), PCLm (0), PCLXL (100), PS (0), PCL (100)
cups-browsed has CUPS-PDF → URF → PDF → PWG → PCLm → PCLXL → PS → PCL

Are there any plans to unify this?

D [25/Sep/2026:11:08:06 +0200] [Job 3] Read cups-browsed-dest-printer option: \"3 ipp://Brother%20DCP-T525W._ipp._tcp.local/ image/urf 600dpi\"
D [25/Sep/2026:11:08:06 +0200] [Job 3] Received destination host name from cups-browsed: printer-uri ipp://Brother%20DCP-T525W._ipp._tcp.local/ image/urf 600dpi
D [25/Sep/2026:11:08:06 +0200] [Job 3] Received job for the printer with the destination uri - ipp://Brother%20DCP-T525W._ipp._tcp.local/, Final-document format for the printer - image/urf and requested resolution - 600dpi

The drvless-generated PPD contains only *cupsFilter2: "application/vnd.cups-pdf application/pdf 0 -", but I assume libppd also checks cupsUrfSupported and adds URF as a filter automatically?

Dominant language
C
Stars
6
Forks
38
Avg merge
23h 9m
Merged PRs (30d)
16

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenPrinting/libppd

All issues in OpenPrinting/libppd

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.