Re: [Gegl-developer] [Gimp-developer] babl roadmap

[Øyvind Kolås <pippin gimp org>]

On Tue, Oct 14, 2014 at 12:34 AM, Elle Stone
<ellestone ninedegreesbelow com> wrote:
> You designed an architecture around converting images to unbounded sRGB for
> editing.
>
> After 6 months of trying to show you that your architecture has serious
> built-in problems, you finally believe me, or at least you believe Mansencal
> and Sayre. But you want to keep the architecture anyway.

We've acknowledged that chromaticities matter for more than the last
half year - and proposed to extend the architecture in ways that
doesn't break other parts of the architecture. We change what we have,
and avoid fixing what isn'r broken - while trying to address
short-coming like you've pointed out.

> So now all chromaticity-dependent editing operations will require a brand
> new "special "specifying"", unless the image is already an sRGB image.
>
> If you didn't intend to convert all images to unbounded sRGB for editing,
> there wouldn't be any reason to "special "specify"" roughly half of all the
> editing operations that you offer through the GIMP UI.

Just like in an ICC based workflow images are converted to unbounded
XYZ for editing? (they are not) The PCS used by a CMS is an
implementation detail; where choices might have been XYZ, linear sRGB
or some other linear RGB; of the preceding linear sRGB has nicer
properties than any of the others.

/Ø