Re: [Gimp-developer] [Gegl-developer] Don't make an architectural mistake based on a groundless premise
- From: Jon Nordby <jononor gmail com>
- To: Elle Stone <ellestone ninedegreesbelow com>
- Cc: gegl-developer-list <gegl-developer-list gnome org>, Øyvind Kolås <pippin gimp org>, Gimp-developer <gimp-developer-list gnome org>
- Subject: Re: [Gimp-developer] [Gegl-developer] Don't make an architectural mistake based on a groundless premise
- Date: Sun, 12 Oct 2014 02:52:44 +0200
On 11 October 2014 13:41, Elle Stone <ellestone ninedegreesbelow com> wrote:
On 10/10/2014 07:49 PM, Øyvind Kolås wrote:
This is not about how images with no embedded profile are handled.
sRGB derived 8bit (and to a lesser degree 16bit) formats are used for
many other things than images with no embedded profile.
You falsely assume that 8-bit images are always sRGB images and that
16-bit integer images are probably sRGB images.
No-one said always. sRGB is however the most common for 8-bit images.
These pixel
formats are crucical for integrating with existing file formats and
libraries;
File formats that only work with sRGB images should not impact
color-managed image editing. Advise the user to convert to sRGB.
Accurate UI colors is a desktop color management issue, entirely
irrelevant to programming a color-managed image editor.
The application needs to interface with the desktop (windowing system).
GIMP uses GTK+ for that, which uses Cairo APIs for rendering - which
basically assumes 8-bit sRGB. I suspect that on X11/Linux these assumptions
go deeper in the graphics stack as well. Yes, it is not right, but such is
the state of things. We will have to improve it step-by-step.
--
Jon Nordby - www.jonnor.com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]