[Openicc] colord Printing Plans, CPD and Gutenprint

[edmund ronald]

I think I will reply in lieu of Robert:

-We are very pleased that Linux is going to be color managed :)

Edmund

On Sat, Feb 26, 2011 at 10:38 PM, Jan-Peter Homann
<homann at colormanagement.de> wrote:
> Hello Richard,
> Would following workflow possible with colord:
>
> - driver setting (e.g. Gutenprint, Turboprint or future printer vemdor
> drivers) have explicit settings with assigned profiles
> - These driver settings are e.g. presented through CPD to the enduser
> - If the user chooses a driver setting in CPD, the assigned profile for the
> driver setting is communicated to colord
> - colord will configure the driver profile in p*toraster
>
> If the driver settings with assigned profiles could be imported in the
> driver, it would be possible to install automatically the correct standard
> profiles through importing the driver setting.
> Also the configuration of the printer profile in p*toraster would be fully
> automatically by choosing a driver setting in CPD or another UI for the
> driver.
>
> ---
> Rendering Intents in colord:
> Any plans, that colord can handle rendering intents (including relatice
> colorimetric with blackpoint compensation)
>
> Question to Robert Krawitz
> - could you imagine to support such a workflow by telling colord which
> profile is valid for a current Gutenprint setting ?
>
> Best regards
> Jan-Peter
>
> Am 24.02.11 14:46, schrieb Richard Hughes:
>>
>> I was talking to the ghostscript guys quite a lot yesterday about
>> changes required for platform icc integration. I'm sharing what I'm
>> doing here in case anyone else wants to give me a hand or has better
>> ideas to share.
>>
>> The basic idea is to teach pstoraster, pdftoraster and foomatic a way
>> to get the best icc output profile for the printed document using
>> colord.
>> The input profiles and rendering intents ideally come from the PDF or
>> PS file, and colord doesn't get involved in this at all.
>>
>> In a hope to understand the architecture I've drawn this diagram:
>> http://colord.hughsie.com/img/cups-plan.png -- corrections welcome.
>>
>> What I've already done:
>>
>> * Rewritten pstoraster from shell to C to allow me to use libdbus with
>> a mainloop
>> * Added code to pstoraster.c and pdftoraster.c to get the desired icc
>> profile from colord
>> * Set the device icc profile for gs>= 9.01
>>
>> What needs to be done:
>>
>> * Add code to foomatic to do the same. I'm no expert in perl, but DBus
>> has a pretty good DBus binding available.
>>
>> Does this sound sane? Ideas and comments welcome. Thanks.
>>
>> Richard
>> _______________________________________________
>> openicc mailing list
>> openicc at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/openicc
>>
>
>
> --
> ----------  Please note the new adress --------------
>
> homann colormanagement --------- fon +49 30 611 075 18
> Jan-Peter Homann ------------ mobile +49 171 54 70 358
> Cotheniusstr. 3 -------- http://www.colormanagement.de
> 10407 Berlin -------- mailto:homann at colormanagement.de
>
>
> _______________________________________________
> openicc mailing list
> openicc at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/openicc
>