All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Sweet <mike@easysw.com>
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: Wed, 17 May 2006 20:23:24 -0400	[thread overview]
Message-ID: <446BBE7C.5090500@easysw.com> (raw)
In-Reply-To: <446BA39A.80802@Sun.COM>

Norm Jacobs wrote:
> 
> 
> 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, ...)

Don't bother listing CUPS here; we will only be using
/usr/share/cups/model for PPD files supplied with CUPS.

> ...
>       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
 > ...

What kind of printer drivers are to be supported by this?  I don't
see what you are trying to do here?

>    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.

FWIW, device ID information is not standardized in IPP, at least not
yet.  Some vendors put the device ID string in printer-info, but that
gets truncated too easily.

 > ...
>    Possibly require/recommend foomatic for LSB 3.2

-1 from me on that one, we've seen too many problems over the years,
and you really only need Foomatic to support legacy Ghostscript
drivers...

-- 
______________________________________________________________________
Michael Sweet, Easy Software Products           mike at easysw dot com
Internet Printing and Publishing Software        http://www.easysw.com

  parent reply	other threads:[~2006-05-18  0:23 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
2006-05-20 15:49   ` Michael Sweet
2006-05-18  0:23 ` Michael Sweet [this message]
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=446BBE7C.5090500@easysw.com \
    --to=mike@easysw.com \
    --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.