From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Any plans for an active color management?
Date: Mon, 17 Feb 2020 19:44:14 +0100 [thread overview]
Message-ID: <37896ab8-4cf7-c5c3-c927-e91f08d812de@xs4all.nl> (raw)
In-Reply-To: <e3543ebe-103e-ecdf-4898-187c2712d35c@klankschap.nl>
On 2/17/2020 6:52 PM, Floris van Manen wrote:
>
>
> On 17-02-2020 16:10, juh wrote:
>> At least, digital images are always RGB.
>>
>> In my special case we started with a RGB corporate design as we are an
>> online cooperative. Print comes later.
>
> The thing is that in print the CMYK will result in a fixed well defined
> object: a physical print on paper. That is then the reference.
> The complete chain of getting the information into print is well defined.
>
> Compare that to the world of digital monitor viewing.
> None is well defined, every monitor and platform has its own unknown
> settings. How would you translate those into a printed document?
>
> So my point was that it might be more convenient to first create the
> publication for print, then let individual pdf browsers do their trick
> in their own environment rendering the CMYK into RGB or whatever...
indeed, start with cmyk when doing print
and given differences in displays one can then just be more tolerant in
how it shows up on screen, as it's unpredictable anyway
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-02-17 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 14:03 Jan U. Hasecke
2020-02-17 14:39 ` Hans Hagen
2020-02-17 14:51 ` Floris van Manen
2020-02-17 15:10 ` juh
2020-02-17 17:52 ` Floris van Manen
2020-02-17 18:44 ` Hans Hagen [this message]
2020-02-17 15:35 ` Henning Hraban Ramm
2020-02-17 16:57 ` Jan U. Hasecke
2020-02-17 18:36 ` Henning Hraban Ramm
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=37896ab8-4cf7-c5c3-c927-e91f08d812de@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).