[argyllcms] Color management in Firefox (was: Re: Color management in

  • From: Kai-Uwe Behrmann <ku.b@xxxxxx>
  • To: ArgyllCMS <argyllcms@xxxxxxxxxxxxx>
  • Date: Wed, 25 Apr 2012 10:15:28 +0200 (CEST)

Date: Mon, 23 Apr 2012 16:22:39 +0200
From: Chris Lilley <chris@xxxxxx>

- lcms removed in 3.5, allegedly due to an lcms security flaw.
 Code size and performance turn out to be the actual reasons.

The reasons look more of some colour management beginners starting on a weekend project to implement a CMM with "only what's really needed". A well trained specialist or better a colour scientist would have seen the value of lcms or any other full fledged CMM as a valuable asset. But projects and companies prefere to hire flat IT engineers, which learn colour management from scratch. Those pure souls must feel overwhelmed by colour management and see it as a burden. I can understand their wish to have something simple, but that's a illusion.

Companies and projects see encryption, font handling, UI design and colour management typical as something to learn over a weekend and then become productive. But these topics are not covered by a plain IT study. Perhaps personal managers learn to hire the right skilled people or these companies continue to burn more money while trying to manage things the hard way and potentially give up.

 Replaced by a Moz-specific library, qcms, with minimal v.2 support and no v.4 

Mozilla mention that this "may result in images being too dark". Yeah, and many 
other problems.

Firefox 3.5 to current (14a1) use qcms

- qcms gets hacked to handle some v.4 profiles by removing the version number 
check and pretending they are v.2 ;)

Benoit Girard  starts working on qcms in 2011

- qcms support for (some of) v.4 added, but disabled, in nightly builds

And now Chromeproject developers continue to hack on qcms.
How much time they could have saved, if they had put that energy into lcms instead? (I know it is a silly question asked many times. Everyone likes to do his own mistakes.)

ocio implements ICC colour management too. But the difference is, they are really comitted to a whole project. And I have no doubt, they get it right. Or Ghostscript in hiring a colour scientist they are very successful around colour.

kind regards
Kai-Uwe Behrmann

Other related posts:

  • » [argyllcms] Color management in Firefox (was: Re: Color management in - Kai-Uwe Behrmann