You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The PPD API of CUPS is deprecated, in favor of the fact that CUPS queues emulate IPP Everywhere printers and all printer capabilities and options could be polled via IPP. This was recently discussed on the CUPS mailing list, thread "PPD API: Status, future and alternatives to handle printer-specific options". So I have done some tests and found some problems, not only the one described here but also Issue #4951 and Issue #4950.
I have a CUPS queue for my HP Deskjet Ink Advantage 2645 All-in-one set up with HPLIP with the attached PPD file.
When I treat this CUPS queue as an IPP Everywhere printer and poll its capabilities via IPP with this command (output file attached)
I get some discrepancies between the options in the PPD file (which the current print dialogs would use) and the options in the IPP record (which a future print dialog would use).
For example the PPD allows setting several print quality levels with different resolutions and the IPP record only tells about a resolution of 300 dpi.
The text was updated successfully, but these errors were encountered:
Understand there is a difference between printer drivers, document formats, and what a printer will support.
Drivers generate printer raster data at various resolutions, however printers consume PWG raster documents at (typically) lower resolutions that are then dithered internally at a higher resolution. So for example a printer that does 1200x600dpi might only accept 300dpi PWG Raster data and internally will dither the 300dpi at 1200x600dpi.
The resolution the printer uses can be controlled by the printer-resolution attribute and/or by the print-quality attribute - the latter is the approach we have chosen to support for CUPS since a) we have no way to convey the printer and document resolution separately and b) exposing 3 print qualities is more user-friendly than exposing 3 print qualities AND N print resolutions.
So while we definitely want to ensure that we expose all of the print qualities supported by the printer, we have no interest in separately exposing all of the printer resolutions that are supported.
The PPD API of CUPS is deprecated, in favor of the fact that CUPS queues emulate IPP Everywhere printers and all printer capabilities and options could be polled via IPP. This was recently discussed on the CUPS mailing list, thread "PPD API: Status, future and alternatives to handle printer-specific options". So I have done some tests and found some problems, not only the one described here but also Issue #4951 and Issue #4950.
I have a CUPS queue for my HP Deskjet Ink Advantage 2645 All-in-one set up with HPLIP with the attached PPD file.
When I treat this CUPS queue as an IPP Everywhere printer and poll its capabilities via IPP with this command (output file attached)
ipptool -tv ipp://till-x1carbon.local:631/printers/printer get-printer-attributes.test > ../cups-queue-hp-clj-cm3530.txt
I get some discrepancies between the options in the PPD file (which the current print dialogs would use) and the options in the IPP record (which a future print dialog would use).
For example the PPD allows setting several print quality levels with different resolutions and the IPP record only tells about a resolution of 300 dpi.
The text was updated successfully, but these errors were encountered: