From: Norm Jacobs <Norm.Jacobs@Sun.COM>
To: printing-architecture <printing-architecture@freestandards.org>
Subject: [Printing-architecture] Meeting notes for 2006-05-17 / LSB 3.2 recommendation
Date: Wed, 17 May 2006 17:28:42 -0500 [thread overview]
Message-ID: <446BA39A.80802@Sun.COM> (raw)
We spent the vast majority of our meeting time discussing what we would
like to
recommend for LSB 3.2. We are also planning on meeting next week at our
normal Wednesday time.
<RECOMMENDATION>
ESPgs 8.15.1 or later with the following drivers compiled in
ijs - InkJet Server
cups - CUPS raster
opvp - OpenPrinting Vector
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
Driver
/usr/lib/printerdriver/{supplier}/...
where whitespace and dash(-) are replaced with with
unserscore(_)
supplier is the ppd file supplier (gutenprint, hplip, cups,
epson,
hp, ...)
/usr/lib/printerdriver/bin/{supplier-executable(s)}
links to executables in the {supplier} directory
Eg.
/usr/lib/prinerdriver/gutenprint/...
/usr/lib/printerdriver/bin/gutenprintijs-5.0 ->
../gutenprint/gutenprintijs-5.0
Installation scripts should be bourne shell and be careful about
portability.
mindful of (sed/awk/...) use lsb tools.
Printer identification
use IEEE 1284 Device Id. In particular, the MFG, MDL, and CMD values
are what we most want to see used (and correctly provided by printer
vendors). This should be the EXACT same value for 1284 parallel,
USB, SNMP, and ultimately IPP query.
MFG - Manufacturer
MDL - Model
CMD - Command Set (PJL, MLC, BIDI_ECP, PCLXL, PCL, PDF,
PJL, MIME,
POSTSCRIPT, ...)
Possibly require/recommend foomatic for LSB 3.2
</RECOMMENDATION>
We discussed including PAPI v1.0 in LSB 3.2, but the issue is that
it needs
to be shipping in a couple of Linux distros before it can be considered.
It's likely that this will have to wait for the next LSB. In the
meantime,
Till is working on including it in the Mandrake cooker.
Norm needs to get some configuration related instructions to Till
for the
PAPI and needs to put the Solaris foomatic-filters changes that he
put into
the CVS main trunk into the stable branch (foomatic-3_0-branch)
Till mentioned filters running as an unprivileged user (lp) and
making sure that
filters didn't use absolute paths in filter chains.
That's about all I remember and the highlights of Wendy's notes.
-Norm
next reply other threads:[~2006-05-17 22:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 22:28 Norm Jacobs [this message]
2006-05-17 23:07 ` [Printing-architecture] Meeting notes for 2006-05-17 / LSB 3.2 recommendation Till Kamppeter
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=446BA39A.80802@Sun.COM \
--to=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.