All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Michael Sweet <msweet@msweet.org>
Cc: "printing-architecture@lists.linux-foundation.org"
	<printing-architecture@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] CUPS 3.x: How we make it converting job data formats?
Date: Sat, 7 May 2022 21:16:20 +0200	[thread overview]
Message-ID: <23e78f69-e63c-2c73-0aab-01be3ecf2d45@gmail.com> (raw)
In-Reply-To: <D7AA9F09-06C6-4F57-9235-5120FE715C8A@msweet.org>

On 07/05/2022 21:04, Michael Sweet wrote:
> Till,
> 
>> On May 7, 2022, at 12:07 PM, Till Kamppeter <till.kamppeter@gmail.com> wrote:
>> ...
>> OK, we will offer both options. It is not our responsibility when the distros accept including Ghostscript, letting the printing stack use Ghostscript, and then use the distro for cloud services (and up to now no one complains about it). I hope it is at least no AGPL violation to use Ghostscript on a regular real-iron computer due to its closed-source BIOS.
> 
> Like I said, the AGPL is not specific enough to exclude this... :/

By all distros including Ghostscript and having it used by their 
printing stack and no one complaining we can assume they have no problem 
with that, but for outside the distro world I will continue to support 
Poppler. Ghostscript delivering high print quality in distros is a good 
advertising for them. CUPS 3.x should also support the two, GHostscript 
to make distros happy, and Poppler for correct commercial use.

    Till

      reply	other threads:[~2022-05-07 19:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26 15:42 [Printing-architecture] CUPS 3.x: How we make it converting job data formats? Till Kamppeter
2022-04-27 12:43 ` Michael Sweet
2022-05-06 15:14   ` Till Kamppeter
2022-05-06 18:22     ` Michael Sweet
2022-05-06 19:18       ` Till Kamppeter
2022-05-06 22:32         ` Michael Sweet
2022-05-07  7:05           ` Till Kamppeter
2022-05-07 13:09             ` Michael Sweet
2022-05-07 14:07               ` Till Kamppeter
2022-05-07 14:45                 ` Michael Sweet
2022-05-07 16:07                   ` Till Kamppeter
2022-05-07 19:04                     ` Michael Sweet
2022-05-07 19:16                       ` 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=23e78f69-e63c-2c73-0aab-01be3ecf2d45@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=msweet@msweet.org \
    --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.