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
That is more or less HP's standard-format PostScript inkjet printers.
What these files have in common is that they have a device ID line beginning with (lower-case D in the end)
*1284DeviceId:
but the Adobe specification shows(UPPER-case D in the end)
*1284DeviceID:
on page 72, near the top (also on page 213 in the list and on page 229).
So the check in scheduler/cups-driverd.c, line 802 should be either for "*1284DeviceID:" or case-insensitive (to work around PPDs with incorrect case).
The text was updated successfully, but these errors were encountered:
First, reassigning the priority - this is a bug in the PPD files, not a CUPS bug per-se.
That said, we'll update cups-driverd and cupstestppd to handle this - cupstestppd will FAIL PPD files with 1284DeviceId and cups-driverd will use a case-insensitive comparison for 1284DeviceID.
Version: 1.2-current
CUPS.org User: till.kamppeter
I have discovered that CUPS is able to list its PPDs with device IDs (in contrary to STR #1552), only it does not work correctly.
Running "lpinfo -l -m" on a Mandriva Cooker installation lets only show the following PPD files (download locations listed here):
All files in http://www.linuxprinting.org/download/PPD/HP/business_inkjet/
http://www.linuxprinting.org/download/PPD/HP/all_in_one/hp_officejet_9100_series.ppd
That is more or less HP's standard-format PostScript inkjet printers.
What these files have in common is that they have a device ID line beginning with (lower-case D in the end)
*1284DeviceId:
but the Adobe specification shows(UPPER-case D in the end)
*1284DeviceID:
on page 72, near the top (also on page 213 in the list and on page 229).
So the check in scheduler/cups-driverd.c, line 802 should be either for "*1284DeviceID:" or case-insensitive (to work around PPDs with incorrect case).
The text was updated successfully, but these errors were encountered: