[Gimp-developer] LAB in Info Window

2010-10-22 Thread jcupitt
 On Thu, 2010-10-21 at 23:23 +0200, Martin Nordholts wrote:
 If someone starts experimenting with this, I suggest making littlecms
 one of potentially backends, so that we can compile against the native
 color management library of a platform when available.

The native CMS is often horribly unreliable and incomplete. The one
that ships with XP, for example, is almost unusable. I think this
component has been replaced now, but the new version is still missing
support for more recent profiles (hope I have that right). Gimp would
need to make at least three Windows binaries: LCMs, XP and Vista+.
They'd produce subtly different results in hard to explain ways.

Photoshop gets around this by having it's own cms and using that on
all platforms. This helps make save files work between platforms too.
I think it would be quite reasonable for GIMP to do the same.

John
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] LAB in Info Window

2010-10-22 Thread Alexandre Prokoudine
On 10/22/10, jcupitt wrote:

 The native CMS is often horribly unreliable and incomplete. The one
 that ships with XP, for example, is almost unusable. I think this
 component has been replaced now, but the new version is still missing
 support for more recent profiles (hope I have that right). Gimp would
 need to make at least three Windows binaries: LCMs, XP and Vista+.

What would be the point of that, when one could implement abstraction
layer for pluggable CMMs and LittleCMS as default CMM? It's what
Scribus team was working on last summer.

Alexandre Prokoudine
http://libregraphicsworld.org
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer