[Openicc] colord 0.1.9 released - CM Framework - Printer Driver
ku.b at gmx.de
Mon Jun 20 06:54:44 PDT 2011
Am 20.06.2011 14:16, schrieb Robert Krawitz:
> On Mon, 20 Jun 2011 14:14:27 +0200, Jan-Peter Homann wrote:
>> - Do you think it would make sense to queue colord for getting the driver setup in a color managed print pipeline ?
> Do you mean to "query" colord? No. It should simply be told what
> settings to use, and use them. There's no good reason for Gutenprint,
> or even just the Gutenprint CUPS driver, to know anything about colord
> or any other kind of profile manager.
To illustrate the shortage of a "hook into the CMS" architecture: What
about one CMS setting the profile int the print spool PDF and an other
one is asked for the driver calibration settings? Usability would be non
reliable and inconsistent. Thats not a nice goal.
>> - If not, what would be you preferred alternative to synchronize printer profile and driver setup ?
> Whatever selects the printer profile should select the driver settings
> (preferably stored in the same blob, so they don't accidentally get
> separated), and simply pass them to Gutenprint.
Agreed. Exactly that route is followed with the XCPD project.
More information about the openicc