From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
"Jan U. Hasecke" <juh+ntg-context@mailbox.org>
Subject: Re: Any plans for an active color management?
Date: Mon, 17 Feb 2020 15:39:52 +0100 [thread overview]
Message-ID: <0a1b3b33-e81e-9ab2-7b8e-12841467a0a9@xs4all.nl> (raw)
In-Reply-To: <6f5009d3-d8c4-5c62-09c2-2dc969739bbd@mailbox.org>
On 2/17/2020 3:03 PM, Jan U. Hasecke wrote:
> Are there any plans to automate these steps into ConTeXt? That would
> enable us to work in RGB the whole time. Only when creating a print pdf
> we would specify a color profile and ConTeXt would do the rest by
> converting all rgb values to cmyk values due to the given color profile.
that would mean plugging some color transfer function into the rgb ->
cmyk conversion that is already there (but i never had to deal with
color transfer functions)
> As this seems very complex I fear that there are no plans to do this.
not unless i know exactly what to do (or am forced to use it myself)
can't you use spotcolors? these are kind of standardized (say pantone)
-----------------------------------------------------------------
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 14:39 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 [this message]
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
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=0a1b3b33-e81e-9ab2-7b8e-12841467a0a9@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=juh+ntg-context@mailbox.org \
--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).