From: Till Kamppeter <till.kamppeter@gmx.net>
To: Norm Jacobs <Norm.Jacobs@Sun.COM>
Cc: printing-architecture <printing-architecture@freestandards.org>
Subject: Re: [Printing-architecture] Meeting notes for 2006-05-17 / LSB 3.2 recommendation
Date: Thu, 18 May 2006 01:07:18 +0200 [thread overview]
Message-ID: <446BACA6.5000604@gmx.net> (raw)
In-Reply-To: <446BA39A.80802@Sun.COM>
Norm Jacobs wrote:
> <RECOMMENDATION>
>
> Installation Locations
> PPD
> /usr/share/ppd/{supplier}/{manufacturer}-{model}.ppd
> where whitespace and dash(-) are replaced with with
> unserscore(_)
> supplier is the ppd file supplier (gutenprint, hplip, cups,
> epson,
> hp, ...)
> manufacturer is the print manufacturer name from the IEEE 1284
> Device ID
> model is the printer model from the IEEE 1284 Device ID
> Eg.
>
> /usr/share/ppd/gutenprint/Hewlett_Packard-hp_color_LaserJet_4650.ppd
> /usr/share/ppd/HP/Hewlett_Packard-hp_color_LaserJet_4650.ppd
>
As some suppliers could have more than one PPD file for the same
printer, for example Foomatic PPDs can exist for one printer used with
different drivers, I suggest to add the driver or whatever is different
in the PPD after the model, separated by another dash. This should
optional but not required. In addition, there should be a directory
level between supplier and PPD for the language:
/usr/share/ppd/{supplier}/{lang}/{manufacturer}-{model}-{extra info}.ppd
/usr/share/ppd/{supplier}/{lang}/{manufacturer}-{model}.ppd
extra-info can be the driver name or anything else which
distiguishes PPDs for the same printer model. Spaces have
to be replaced by underscores, as usual.
Examples:
/usr/share/ppd/foomatic/en/HP-LaserJet_4-hpijs.ppd
/usr/share/ppd/foomatic/en/HP-LaserJet_4-ljet4.ppd
/usr/share/ppd/foomatic/en/HP-LaserJet_4-opvp_pcl5e.ppd
/usr/share/ppd/HP/en/Hewlett_Packard-hp_color_LaserJet_4650.ppd
/usr/share/ppd/HP/de/Hewlett_Packard-hp_color_LaserJet_4650.ppd
[...]
> Possibly require/recommend foomatic for LSB 3.2
>
Another question: What is "Linux Standards Base" really about? Only
LINUX or also BSD, Solaris, ...
In case of only Linux we could even require CUPS ...
> </RECOMMENDATION>
Till
next prev parent reply other threads:[~2006-05-17 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 22:28 [Printing-architecture] Meeting notes for 2006-05-17 / LSB 3.2 recommendation Norm Jacobs
2006-05-17 23:07 ` Till Kamppeter [this message]
2006-05-20 15:49 ` Michael Sweet
2006-05-18 0:23 ` Michael Sweet
2006-05-18 17:34 ` Till Kamppeter
2006-05-18 19:43 ` Michael Sweet
2006-05-18 19:50 ` Till Kamppeter
2006-05-18 20:00 ` Michael Sweet
2006-05-20 13:42 ` Ian Murdock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=446BACA6.5000604@gmx.net \
--to=till.kamppeter@gmx.net \
--cc=Norm.Jacobs@Sun.COM \
--cc=printing-architecture@freestandards.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.