From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: color (rendering) intent
Date: Tue, 11 Aug 2015 10:03:30 +0600 [thread overview]
Message-ID: <26AA615A-5625-4E88-9A25-FF0E7A5C6987@fiee.net> (raw)
In-Reply-To: <55C8F7B2.4020807@gmx.net>
Am 2015-08-11 um 01:12 schrieb Peter Rolf <indiego@gmx.net>:
>>> Thank you! So I can document that key for \setupcolors? (Does it do
>>> anything? Different from \setupbackend?)
>>
>> it should add some group info in the pdf
>
> If I remember correctly this sets the complete document (global) to
> 'overprint' (or 'knockout'). Only useful for grayscale only documents.
> Don't set this parameter, if you want to use local overprinting (or
> knockout)! There should be a warning about this in the documentation.
>
> The \setupcolors setting is also far older than the PDF/A|X related
> output 'intent' parameter in \setupbackend. No direct relation other
> than that both parameters are prepress options.
Thank you, I documented that in http://wiki.contextgarden.net/Command/setupcolors
Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2015-08-11 4:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 8:28 Henning Hraban Ramm
2015-08-10 11:52 ` Hans Hagen
2015-08-10 15:23 ` Henning Hraban Ramm
2015-08-10 16:58 ` Hans Hagen
2015-08-10 19:12 ` Peter Rolf
2015-08-11 4:03 ` Henning Hraban Ramm [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=26AA615A-5625-4E88-9A25-FF0E7A5C6987@fiee.net \
--to=texml@fiee.net \
--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).