re: 3C K in Quark
re: 3C K in Quark
- Subject: re: 3C K in Quark
- From: Henrik Holmegaard <email@hidden>
- Date: Tue, 17 Apr 2001 08:22:08 +0200
miro franz <email@hidden> wrote:
I want to recommend NOT using
Quark's CMS and I need to have a good solid reason
why.
a. QuarkXPress wants to let you print through both the QuickDraw and
PostScript pipeline. The QD pipeline only accepts RGB, so text
'black' is defined as RGB. Then if you print to a PS device, it's up
to the PS device what to do with that RGB, as it can't image it, it
must convert it one way or another. You can define a custom color for
your QXP text, of course. Define your text as K 100% and you're OK
going to a PS printer but not to QD. InDesign defines text 'black' as
K 100% by default as it's designed from the ground up to print only
through the PS pipeline. ICC color servers including Helios and
iQueue will pick up vector objects defined as R0 G0 B0 and force them
to K 100%, not only for QXP but also for Word and other apps that
don't write their own PostScript.
b. QuarkXPress only color manages raster objects, not subsets of
PostScript including EPS and PDF versions. These pass through to the
RIP where you don't know what happens. The same is true of InDesign
by the way. In both cases you must place an ICC color server like
iQueue downstream from the layout application. At a simpler level the
main reason not to use the Quark CMS is that as Helios points out,
for every profile you change, every image in the whole job is
reimported. And that takes forever. By comparison the old Helios
ColorSync XTension for QuarkXPress 3X is much faster.
I'm pulling my hair out.
Hmm...you must be new to ICC color management since you've still got
some left to pull at -:).
--
Henrik Holmegaard
TechWrite, Denmark