[Openicc] colord 0.1.9 released - CM Framework - Printer Driver

[Kai-Uwe Behrmann]

Am 20.06.2011 16:53, schrieb Richard Hughes:
> On 20 June 2011 15:47, Michael Sweet <msweet at apple.com> wrote:
>> If you assign a device profile at spool time ... then you should also assign the driver options...
> I'm not sure I follow that logic. If I embed a profile, lets say
> "Hughsie's HP Photosmart Glossy Paper" then that's the calibrated
> condition I want to print with. Of course, if we have an embedded
> output profile, then it's probably not a good idea to query colord and
> override the color profile the user has carefully chosen in the
> application. If the embedded profile has the Gutenprint xml file
> embedded in the DICT then it can easily be used instead. What will
> happen in 99.99% of apps is they won't care and we don't get any
> embedded output profile at all. That's where the data from colord is
> useful.

If Gutenprint could see the PDF file, which it can't,  and could extract
the GUTENPRINT_settings from the PDFs OutputIntents meta tag, then it
could at least check things are going on correctly. But it can't.

As we are about percentages: if that 0.01 % is the one where profiling
mishappens because Gutenprint disconnects the actual target print job by
quering to some random CMS, then thats not going to work for say 50% of
users.

regards
Kai-Uwe
-- 
www.behrmann.name www.oyranos.org