[Openicc] GoSoC 2011: CPD and Softproofing
almccart at lexmark.com
Tue May 3 09:51:43 PDT 2011
"Does it make sense to embed it into the ICC profile itself (i.e., changing
the profile on disk file, and changing the checksum)"
The driver settings that affect the color behavior of the printer should be
installed into the printer profile as it is built.
So this is not a post-build change to the profile -- it is a fingerprint of
the appropriate settings of the associated color processing path and the
printer that should be instantiated anytime that profile is used.
Conversely, for any print job, when the user selects the values of all of
the print parameters and selects the media to be used -- those selections
point to a profile.
Keep in mind that the profiles for printing are not 'printer profiles' ---
rather they are print condition profiles. The selection of the correct
profile for a print job depends on the paper, ink, and other driver settings
as well as the print device itself.
Ann L McCarthy
Imaging Systems R&D
Lexmark International, Inc.
On Tue, May 3, 2011 at 12:25 PM, Richard Hughes <hughsient at gmail.com> wrote:
> On 3 May 2011 17:08, Jan-Peter Homann
> > Here, the idea of embedding the driver settings into the ICC profile via
> > dictType Metadata is a very big help.
> Does it make sense to embed it into the ICC profile itself (i.e.,
> changing the on disk file, and changing the checksum) or just to save
> it as metadata on a meta-profile object such as used in colord?
> This is the sort of metadata that is added using SetProperty() and
> stored in the persistent database that is optionally stored across
> reboots and device hotplug events. See
> http://colord.hughsie.com/api/Device.html#Device.SetProperty for more
> openicc mailing list
> openicc at lists.freedesktop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openicc