[Openicc] ICC meta tag in device profiles

Kai-Uwe Behrmann ku.b at gmx.de
Wed Oct 27 03:00:52 PDT 2010


Am 27.10.10, 10:28 +0100 schrieb Richard Hughes:
> On 27 October 2010 09:40, Kai-Uwe Behrmann <ku.b at gmx.de> wrote:
>> If you reread, you might see that the device and driver information is
>> already inside the ICC profile, which is the matter of the article.
>
> Well, I wanted to be able to match to udev properties, and things like
> that. I couldn't find a spec page anyware.

Can you outline the udev properties? How do they relate to which device 
classes?

>> I would not go with underscore which can easily collide with vendor strings.
>> As well I disagree with many false statements on your side. Or can this page
>> just be called biased writing?
>
> Sure, I'm biased to GCM, I'm sure there is no surprise there.

kolor-manager is explicitely mentioned with new features in my original 
post. And you answere with a link to a page under your control which 
still states that that very project is dead. Biased was only a polite 
expression. If you want to criticise stay on facts not fiction and skip 
such unpolite links. We are not on the Gnome marketing channel here.

>> * assign device to ICC - store the above infos in the ICC profile
>>  itself, where to do best?
>
> This is what worries me. What if the same profile is associated with
> two monitors? The mapping would have to deal with situations like
> this. If you just encode "this profile maps to device with edid md5
> AC4DE5A.." then that won't work.

Then a profile editor needs to be in place to remove the serial entry for 
instance and remain the colorimetrical, manufacturer and model strings or 
extend those string to certain values and ranges. I would suggest IccXML 
for that. A tutorial could explain howto.

kind regards
Kai-Uwe Behrmann
-- 
developing for colour management 
www.behrmann.name + www.oyranos.org


More information about the openicc mailing list