From: Till Kamppeter <till.kamppeter@gmail.com>
To: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] Deprecation of all modules except for everywhere
Date: Mon, 25 Oct 2021 17:19:14 +0200 [thread overview]
Message-ID: <d263b5ce-4a76-5dd2-6e2b-88a0dfcaef24@gmail.com> (raw)
In-Reply-To: <1880865.CGEiM1yXm4@cwolf-work>
On 25/10/2021 16:36, Christian Wolf wrote:
> Hello,
>
>> Classic CUPS printer drivers are replaced by Printer Applications and
>> Printer Applications are emulations of IPP Everywhere printers. With
>> trhis all printers will appear as IPP Everywhere (or driverless IPP)
>> printers. The modern ones do this already by themselves, for the old
>> ones we use Printer Applications.
>
> so, I see there is a fallback plan in place. If I understand this correctly,
> one mainly sourced the usage of PPDs out into standalone applications so the
> CUPS core is free of bloat. Makes sense.
>
Generally, Printer Applications do not use PPDs. One can use any
architecture to get an emulation of an IPP printer. LPrint for example
does not use PPD files internally, same for the sample Printer
Application in the PAPPL project.
For PostScript printers, where the manufacturer provides a PPD file, and
also for classic CUPS drivers for old printers where I do not have
access to for testing, the easiest way to go is to have an architecture
which wraps the classic CUPS driver with its PPD files into a Printer
Application. For this I have created the pappl-retrofit
(https://github.com/OpenPrinting/pappl-retrofit) library with which I
have maded my 4 Printer Applications to retro-fit practically all free
software CUPS drivers which are available as *.deb packages in the
Debian distribution.
Till
prev parent reply other threads:[~2021-10-25 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 13:25 [Printing-architecture] Deprecation of all modules except for everywhere Christian Wolf
2021-10-25 13:32 ` Zdenek Dohnal
2021-10-25 13:44 ` Till Kamppeter
2021-10-25 14:36 ` Christian Wolf
2021-10-25 15:19 ` Till Kamppeter [this message]
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=d263b5ce-4a76-5dd2-6e2b-88a0dfcaef24@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=printing-architecture@lists.linux-foundation.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.