[Openicc] compiz-cms/CompICC [was: What is exactly needed...]
ku.b at gmx.de
Tue May 31 08:32:30 PDT 2011
Am 31.05.11, 17:12 +0200 schrieb Gabriel Ebner:
> On Tue, May 31, 2011 at 5:06 PM, Kai-Uwe Behrmann <ku.b at gmx.de> wrote:
>> Am 31.05.11, 16:48 +0200 schrieb Gabriel Ebner:
>>> On Tue, May 31, 2011 at 4:29 PM, Richard Hughes <hughsient at gmail.com>
>>> There is also an Oyranos-free compiz color correction plugin:
>> compiz-cms would break all applications, which rely on _ICC_PROFILE(_xxx)
>> atoms as it has currnetly not automatism to avoid double colour correction.
>> This means Krita, Gimp, Inkscape, Scribus and so on would break colour wise.
> It breaks *less* applications than compicc, since it doesn't rely on
> the applications to implement the net-color spec (which none of the
The net-color spec ensures that above mentioned applications run inside a
virtual sRGB environment without double colour correction. The
applications run colour management wise automatically correctly, even
though not fully utilising a wide gamut monitor.
> above implements), but instead allows you to manually specify a
> whitelist for color-managed applications.
That approach will require users some try and error to figure out, which
applications shall be listed and which not. That a error proune procedure.
Developers from some of the above applications objected strongly against
such a behaviour in the past.
> I'm running compiz-cms on all my machines, all the time -- which was
> not possible with compicc, exactly because compicc broke Firefox,
> Gimp, and every other color managed application.
As far as I could check CompICC worked always as expected and correctly.
Moreover it is designed to do so.
Can you give reasons for that "compicc broke Firefox, Gimp" statement?
developing for colour management
www.behrmann.name + www.oyranos.org
More information about the openicc