Re: Why don't drivers use a CMYK profile?
Re: Why don't drivers use a CMYK profile?
- Subject: Re: Why don't drivers use a CMYK profile?
- From: Henrik Holmegaard <email@hidden>
- Date: Mon, 13 Nov 2000 08:30:26 +0100
Dan Caldwell wrote:
The real reason that any OS level print drivers do not use CMYK
profiles is that neither Microsoft or Apple OS is capable of sending
CMYK data from the OS. The only way a printer can receive CMYK (or
more channels) is via Postscript.
Yes.
The lack of a CMYK imaging model within the OS is true both for
QuickDraw and Graphics Device Interface (GDI).
This is why PostScript has become an add-on operating system, instead
of just a plain Page Description Language. If Apple had instituted a
robust CMYK imaging model in the OS, we could strip all the color
stuff out of PostScript Level 2 and 3 and live happily ever after -:).
It is also the reason we need ICC, simply because each and every
application that took advantage of PostScript Level 1 to control the
ink densities on the press (for which PostScript was necessary), also
developed its very own RGB to CMYK and CMYK to RGB conversion
technology, leading to an awfull mess of desktop formats in addition
to the link-type RGB to CMYK device dependent conversions used in the
old high-end CEPS systems.
--
------------------------------------------
Henrik Holmegaard, TechWrite
Stationay +45 3880 0721 - +45 3881 0721
Mobile +45 2178 3959
Toelloesevej 69, 2700 Broenshoej, Denmark
------------------------------------------