[Openicc] colord 0.1.9 released - CM Framework - Printer Driver
rlk at alum.mit.edu
Mon Jun 20 05:16:49 PDT 2011
On Mon, 20 Jun 2011 14:14:27 +0200, Jan-Peter Homann wrote:
> Hello Richard and all,
> As I´m not a developer, I still have to learn about the communication between the CM Framework and CUPS, ..toraster printer driver and so on... (e.g. about the differences of sendind and queuing...)
> I agree, that the CM Framework should not need to know the details about driver setup. It would be just enough, if it provides one XML-file for the driver (e.g. Gutenprint).
> - What would be the amount of work for the Gutenprint team to queue colord for the driver setup of a given printjob ?
> - 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.
> - 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.
More information about the openicc