[Openicc] What is exactly needed for color management ... driver setup PPD

[Jan-Peter Homann]

Hello Robert and all,
We have distinguish two use cases of the DICT key

1) synchronizing the target profile in gstoraster with setting of Gutenprint
This can be solved through embedding the complete serialized Gutenprint 
setting as Metadata into the printer profile.
This could e.g. be:

KEY: "Gutenprint"
VALUE: "XML_Gutenprint_setting"

2) usage of qualifiers in the printing GUI (e.g. CPD)
Here I still don´t get the point, how the workflow will be. So far as I 
understand, the printing GUI (e.g. CPD) presents the user the options, 
which are encoded in the PPD.

If we allow the user to install ICC profiles with embedded Gutenrint 
driver setting independent from the driver itself, we either need a 
mechanism for updating the PPD, or to deal with the qualifiers in the 
printing GUI independently from the PPD.
This could be e.g. solved if, the qualifiers are independent DICT 
entries like e.g.

KEY: "mediatype"
VALUE: plain

KEY: "quality"
VALUE: "draft"

The CM Framework like e.g. g-c-m / colord or Oyranos parses all 
installed profiles for a printer and makes the qualifiers of the 
profiles available to the printing GUI (e.g. CPD)

The altentaive would be, that the CM frameworks updates the qualifier 
entries in the PPD and the Printing GUI presents the new PPD entries to 
the user.


Best regards
Jan-Peter

Am 01.06.11 02:10, schrieb Robert Krawitz:
> On Tue, 31 May 2011 21:44:27 +0100, Richard Hughes wrote:
>> On 31 May 2011 21:13, Jan-Peter Homann<homann at colormanagement.de>  wrote:
>>> Is it correct, that you are using the cupsICC qualifier specified in the PPD
>>> of the printer, for doing the described match of printer profile and driver
>>> setting ?
>> Correct -- See http://colord.hughsie.com/faq.html#qualifiers
>>
>>> this leads for me for more questions:
>>>
>>> - Is it possible to prepare a printer profile, that it will automatically
>>> match the corrects cupsICC qualifiers for a given printer ?
>> Yes, although we haven't actually sat down and defined a DICT key and
>> value format that can be used in colord and oyranos. I suppose it
>> could be something like:
>>
>> KEY:  "QUALIFIER_defaults"
>> VALUE: "RGB.Glossy.*,RGB.Plain.*"
>>
>> KEY:  "COLORD_objectid"
>> VALUE: "cups-Photosmart-B109a-m"
>>
>> But better ideas certainly welcome.
> Just make sure the value can be arbitrarily large, so that we can pass
> a serialized Gutenprint settings object through this.  That settings
> object might include LUTs for each channel, with up to 65536 values
> per channel expressed in text format floating point number.  In other
> words, a limit of less than a megabyte or thereabouts could get us
> into trouble, and once it's that large, you might as well forget about
> limits.
>


-- 
----------  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