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>,
Jay Berkenbilt <ejb@ql.org>, Vikrant Malik <vikrant@iitk.ac.in>
Subject: Re: [Printing-architecture] Make use of extended color spaces on IPP printers
Date: Sat, 8 May 2021 00:11:51 +0200 [thread overview]
Message-ID: <fdd1654d-8dd6-9eb8-e41d-dcf786c559d1@gmail.com> (raw)
In-Reply-To: <FC95906E-6085-4121-AEA8-9E53613872AD@msweet.org>
On 07/05/2021 21:53, Michael Sweet wrote:
>> TL;DR: Some doubts about supporting extended color depth and color spaces:
>> - How to discover if a page in a PDF is 8/16-bit color/grayscale
>> sRGB/Adobe RGB?
>
> So there are ways to do this, but none are pretty... :/
>
Are they somewhere documented? Is there sample code? Is it worthwhile to
implement it? Does implementing it take less new lines in cups-filters
than cups-filters already has?
If it is too complicated, I think the most intuitive solution, at least
for the high color depth is to trigger it by print-quality=high.
WDYT, would it also make sense to also switch to Adobe RGB (if available
on the printer) if the user sets print-quality=high?
>> - How important is Adobe RGB for printing? If a printer advertises that
>> it supports it, is it worthwhile for us to support jobs in Adobe RGB?
>
> Very important, since a lot of cameras use AdobeRGB (or provide an option for it) for an expanded color gamut. And if you are going from Display P3 (which is another one you'll see a lot of from iPhones/iPads) it is even more important since sRGB is a really small color space.
>
For printing photos from photo applications the incoming PDF is probably
raster-only and could be treated with pclmtoraster and so an easy way to
determine whether it is AdobeRGB, but if it is an actual vector PDF it
gets more difficult. And what does one do with Display P3? Is it
mentioned in PWG/IPP/Apple Raster/PWG Raster/Mopria? Is it well known,
is there a free solution to convert it to Adobe RGB?
>> - How is all this influenced by the "print-content-optimize" setting?
>
> Two different things - certainly the 'photo' value might be hint that AdobeRGB/deep color is useful/important, but I'd also say that "print-quality" can also feature in this decision, e.g., 'high' (5) print quality might indicate deep color is preferred.
>
OK, probably I will trigger it by the high quality setting. Important is
to know whether I can simply switch to Adobe RGB (only if printer has
Adobe RGB) regardless of the incoming job and the printer does always
the right thing (and not try to print sRGB unconverted as Adobe RGB or
uses a conversion with significant quality loss).
> So print-color-mode and pwg-raster-document-type-supported/urf-support do two different things. "print-color-mode" is a rendering intent (color, grayscale, bi-level, etc.) while the others list the actual color spaces and bit depths that are supported.
OK.
Till
next prev parent reply other threads:[~2021-05-07 22:11 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 17:46 [Printing-architecture] Human-readable strings for standard IPP options/choices/attributes/propertirs Till Kamppeter
2021-04-27 18:02 ` Michael Sweet
2021-04-27 18:10 ` Till Kamppeter
2021-04-28 8:17 ` Till Kamppeter
2021-04-28 11:43 ` Michael Sweet
2021-05-07 18:52 ` [Printing-architecture] Make use of extended color spaces on IPP printers Till Kamppeter
2021-05-07 19:53 ` Michael Sweet
2021-05-07 22:11 ` Till Kamppeter [this message]
2021-05-08 0:04 ` Michael Sweet
2021-05-08 23:52 ` Solomon Peachy
2021-05-09 1:24 ` Michael Sweet
2021-05-09 2:24 ` Solomon Peachy
2021-05-09 2:54 ` Michael Sweet
2021-05-09 8:20 ` Till Kamppeter
2021-05-09 13:41 ` Michael Sweet
2021-05-09 14:03 ` Solomon Peachy
2021-05-09 20:32 ` Michael Sweet
2021-05-09 19:26 ` Till Kamppeter
2021-05-09 20:34 ` Michael Sweet
2021-05-09 20:43 ` Till Kamppeter
2021-05-09 21:03 ` Michael Sweet
2021-05-08 22:45 ` Till Kamppeter
2021-05-09 1:38 ` Solomon Peachy
2021-05-09 9:20 ` Till Kamppeter
2021-05-09 13:49 ` Michael Sweet
2021-05-09 20:14 ` Till Kamppeter
2021-05-09 20:55 ` Michael Sweet
2021-05-09 21:31 ` Till Kamppeter
2021-05-10 1:08 ` Michael Sweet
2021-05-27 18:04 ` Till Kamppeter
2021-05-27 19:04 ` Solomon Peachy
2021-05-28 12:59 ` Michael Sweet
2021-05-29 19:19 ` Till Kamppeter
2021-05-29 22:32 ` Michael Sweet
2021-05-30 19:56 ` Till Kamppeter
2021-05-30 20:53 ` Michael Sweet
2021-05-30 21:50 ` Till Kamppeter
2021-05-31 3:12 ` Michael Sweet
[not found] ` <d5082b23-8eb7-be84-db5c-42bdde3ba5ac@canonical.com>
2021-05-31 13:24 ` Michael Sweet
2021-05-31 15:03 ` Till Kamppeter
2021-05-31 18:13 ` Michael Sweet
2021-05-31 19:38 ` Till Kamppeter
2021-06-01 0:54 ` Michael Sweet
2021-05-25 17:43 ` Till Kamppeter
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=fdd1654d-8dd6-9eb8-e41d-dcf786c559d1@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=ejb@ql.org \
--cc=msweet@msweet.org \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=vikrant@iitk.ac.in \
/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.