[Openicc] CUPS Color Management under Linux gets into distros

[Cyrille Berger Skott]

On Wednesday 02 March 2011, Kai-Uwe Behrmann wrote:
> >>> The underlaying issue is that the paint engine should allow apps to
> >>> paint images in formats other than QImage (IE. a jpeg or tiff) and the
> >>> backend should parse the image for things like ICC profiles and it
> >>> should use those as part of the output stream if the actual paint
> >>> device support these like a PDF device can.   Or QImage needs to be
> >>> extended to support this meta data and higher bit depths. I suspect
> >>> that the Qt folks would argue that you can open most image formats as
> >>> a QImage so is unnecessary to allow painting in native file formats
> >>> but this ignores that fact that the process of opening a tiff or jpeg
> >>> image as a QImage discards almost all of the meta data that is part of
> >>> that image including ICC profiles. In addition it flattens the image
> >>> to a max of 8 bits/channel.
> >> 
> >> Qt appears here like on the same level as Google. They are make things
> >> less than just simple.
> > 
> > I think it is the opposite.  They have made things too simple and
> > everything has been reduced to a lowest common denominator.   As a
> > result they are doing
> 
> Almost agree, but it looks to me that they are already below the lowest 
> common denominator. They omit the whole colour management area outside
> sRGB. And I do not see the justification.
Lack of demand ? Have you noticed how few applications integrate a proper 
color management workflow ? Developers are generally unaware, and users blame 
their printers/screens/camera for poor qualities. Educating people and filling 
bug report is the way to go.

-- 
Cyrille Berger Skott