[Openicc] GoSoC 2011: CPD and target printing
graeme at argyllcms.com
Thu May 12 22:07:32 PDT 2011
Michael Sweet wrote:
> Actually not unless you plan on having that application apply the device profile you
But this is exactly the point! You want everything else the same, except
the color processing, which should pass the device values through unchanged.
The best arrangement is actually to label the print file with some
special key, so that it always prints with device values, without
setting anything in the print dialog. The print dialog should show
though that the file is being printed in device space.
The problem is that there is no standardized way of marking documents
in this way (with the possible exception of certain versions of PDF),
so it has to be some "out of band" method like PS or PDF comments,
or some new TIFF tag.
[Note that the reality is much more complicated that just disabling
source colorspace processing when printer setup and calibration
is to be done - see my post a few days ago about the "4 printing modes".]
> I hope that kind of workflow disappears in favor of a common profile registry
> that is used when printing from any application. Application-based color management has
> a long history of not working reliably...
How does this profile registry magically get created ? Someone needs
to profile the devices. No-one can, without a means to do so!
There are also people who need to move beyond conventional ICC
based profile color management, ie. they want real gamut mapping,
not the broken gamut mapping that ICC provides. So for things
like high quality transformations (ie. device link transforms)
or image dependant gamut mapping, something no normal CMM
provides, "application" color management is the only way.
If you don't provide such a capability on your platform,
the color professionals (like photographers) will move off your
platform, and recommend everyone else does too!
More information about the openicc