[Openicc] colord Printing Plans

Graeme Gill graeme at argyllcms.com
Thu Feb 24 17:11:39 PST 2011


Chris Murphy wrote:
> I admit this is unique on Linux. On Mac OS and Windows, the legacy RGB path is not
> PostScript but QuickDraw and GDI, and for Mac OS today now that QuickDraw is deprecated
> it is Quartz which can do either RGB or CMYK.

This may be so for color unsophisticated applications, but anything sophisticated
has used "PostScript Bypass" to inject its own PS into the print job on MSWin and Mac.

> it in the first place. If the application is seriously producing untagged data across
> the board including saving out its own document format, then neither that developer nor
> its users really care one bit about color. I am not opposed to the idea of building

This isn't strictly true. They expect DeviceXXX to be a "reasonable" color space,
not the actual device colorspace. For RGB that means something that compares
to what they see on their display. For CMYK, that means something that compares
to a standard printing press or the Pantone CMYK swatches. Any system that is to be
regarded as having satisfactory color, meets these expectations. (Take that as a
lesson from spending 10 years developing PS RIPS).

Graeme Gill.


More information about the openicc mailing list