Reuben,

I just noticed you are right. In CUPS webinterface there is a manufacturer 
indication "HP" and "Hewlett-Packard" on Ubuntu 6.06 LTS.
It were indications "HP" and "HP (HPLIP)" that were merged around april in 
Dapper after many bug reports.

To me it is more than clear now that different manufacturer indications cause 
lots of user confusion and problems.
According to the PPD Specification 
(http://partners.adobe.com/public/developer/en/ps/5003.PPD_Spec_v4.3.pdf) a 
manufacturer must use the same *Manufacturer name string in each of their PPD 
files. Also, the string must be unique among manufacturers; two or more 
manufacturers may not use the same string. This Specification also provides a 
list of the current known manufacturer
strings which says that for Hewlett Packard printers the *Manufacturer: "HP" 
must be used!

The "Hewlett-Packard" manufacturer indication comes from PPDs installed by 
package foo2zjs.
Also a "MINOLTA-QMS" manufacturer indication is used in PPDs from package 
foo2zjs while package foomatic-filters-ppds uses "Minolta" in its PPDs.
Also a "Dymo" manufacturer indication is used in Dymo.ppd included with cypsys 
package while "Dymo-CoStar" is used in PPDs from package foomatic-filters-ppds.

I think this can easily be verified in e.g. CUPS webinterface,
developers should do this before releasing a new version of Ubuntu and
make the necessary changes in the Debian packages containing prebuilt
PPDs.

I'm reopening this bug and reassigning to foo2zjs.
Changing description to: HP PPDs installed by foo2zjs should use *Manufacturer: 
"HP"

** Summary changed:

- Foomatic missing LaserJet 4L / suggestions
+ HP PPDs installed by foo2zjs should use *Manufacturer: "HP"

** Changed in: foomatic-db (Ubuntu)
Sourcepackagename: foomatic-db => foo2zjs
       Status: Rejected => Confirmed

-- 
HP PPDs installed by foo2zjs should use *Manufacturer: "HP"
https://launchpad.net/bugs/50631

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to