From: Tobias Hilbricht <hilbricht@linopus.de>
Subject: Re: Black generation in cmyk output
Date: Tue, 07 Dec 2004 10:40:35 +0100 [thread overview]
Message-ID: <1102412435.5012.74.camel@phoebus.venus.bay> (raw)
In-Reply-To: <41AEEA2B.4090407@elvenkind.com>
Am Do, den 02.12.2004 schrieb Taco Hoekwater um 11:10:
> Just curious: why do you need a cmyk pdf document?
Of course you can leave colour space conversion and colour separation to
the printer (provided the printer has the means to do so). However, for
full control over the print colours it is better to have a calibrated
monitor and a document in the CMYK colourspace - then you see what the
colours a likely to look like, and dependency on the printer is reduced.
Agencies, which prepare graphics for advertisements, pay thousands of
Euros to be able to control the correct outcome of corporate colours or
skin colours, for example.
Yours sincerely
Tobias Hilbricht
next prev parent reply other threads:[~2004-12-07 9:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 15:06 Piotr Kopszak
2004-11-30 15:22 ` Taco Hoekwater
2004-11-30 23:19 ` Tex Live 2004 + context Ciro A. Soto
2004-11-30 23:45 ` Patrick Gundlach
2004-11-30 23:52 ` Ciro A. Soto
2004-12-01 0:36 ` Patrick Gundlach
2004-12-01 8:19 ` Taco Hoekwater
2004-12-01 9:22 ` VnPenguin
2004-12-01 9:39 ` Adam Lindsay
2004-12-01 10:45 ` VnPenguin
2004-12-01 14:19 ` Black generation in cmyk output Piotr Kopszak
2004-12-01 16:31 ` Henning Hraban Ramm
2004-12-01 16:52 ` Hans Hagen
2004-12-02 9:40 ` Piotr Kopszak
2004-12-02 9:46 ` Hans Hagen
2004-12-02 10:10 ` Taco Hoekwater
2004-12-03 8:21 ` Christopher Creutzig
2004-12-03 10:00 ` Piotr Kopszak
2004-12-03 10:15 ` Taco Hoekwater
2004-12-03 17:23 ` Siep Kroonenberg
2004-12-07 9:40 ` Tobias Hilbricht [this message]
2004-12-07 10:56 ` Siep Kroonenberg
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=1102412435.5012.74.camel@phoebus.venus.bay \
--to=hilbricht@linopus.de \
--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).