From: Till Kamppeter <till.kamppeter@gmx.net>
To: Michael Sweet <mike@easysw.com>
Cc: Norm Jacobs <Norm.Jacobs@Sun.COM>,
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 21:50:54 +0200 [thread overview]
Message-ID: <446CD01E.7020002@gmx.net> (raw)
In-Reply-To: <446CCE7F.4070501@easysw.com>
Michael Sweet wrote:
> Till Kamppeter wrote:
>
>> ...
>> CUPS driver scripts and backends must go into /usr/lib/cups/filter and
>> /usr/lib/cups/backend, either physically or as a symbolic link from
>> files in /usr/lib/printerdriver/{supplier}/.
>
>
> That's actually not necessary. You can (and most vendors do, on
> MacOS X) put a full path to the filter in the PPD file.
>
>> ...
>> So If we really say LSB is the LINUX Standards Base, we can let the LSB
>> 3.2 require CUPS 1.2.x or newer, ESP GhostScript 8.15.2 or newer (to
>> serve pswrite, pdfwrite, cups, ijs, opvp), KDE Print, GTK Print, PAPI
>
>
> Agreed.
>
>> If we want the LSB standard to be a standard for all Unixes (then they
>> should rename to USB perhaps) then we can only require more abstract
>> standards, especially PAPI, so that ISVs do not need to care about the
>> spooler used on the destination system. In that case also Foomatic
>> should be required by the standard, as it interfaces the same driver
>> (including CUPS raster drivers) to many different spoolers, including
>> CUPS, BSD LPD, and Solaris LP.
>
>
> Does Foomatic do file type detection and conversion (i.e. the whole
> CUPS filter chain)?
>
It delegates file type conversion to a2ps (or another converter, it is
configurable). Norm, feel free to add more sophisticated file type
conversion functionality.
Till
next prev parent reply other threads:[~2006-05-18 19:50 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
2006-05-18 17:34 ` Till Kamppeter
2006-05-18 19:43 ` Michael Sweet
2006-05-18 19:50 ` Till Kamppeter [this message]
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=446CD01E.7020002@gmx.net \
--to=till.kamppeter@gmx.net \
--cc=Norm.Jacobs@Sun.COM \
--cc=mike@easysw.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.