Dear Alan
I thought the responsibility of libjpeg was to encode and decode jpegs.
And I thought "decode" meant "give me pixels I can push to my screen", not
"make me parse the file myself to find metadata chunks".
Here's my growing list of programs in Debian that choke on YCCK jpegs,
Well, the point here is that YCCK is created NOT for display on screen,
but for print!
Look at your monitor and you will notice that it doesn't have CMYK
components.
Look at your printer and you will notice that it doesn't have RGB
components.
So these are distinct output areas.
The screen people were kind enough to create something like
IEC 61966-2-1 (sRGB) for common image interchange, and later
came an amendment for sYCC and so on (this is used in digital cameras).
The print people were not kind enough to create a corresponding
amendement for YCCK and so on, because they don't care for
common image interchange as much as the screen and camera people do.
It is simply not part of their business model, you have to understand
that.
So if they don't care for common image interchange, why should
anybody else do their work?
So either you do it yourself, or you have to accept the situation.
Regards
Guido
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
