On Sat, Aug 03, 2013 at 12:48:24AM +0000, Alan Curry wrote:
> Package: libjpeg-progs
> Version: 8d-1
> Severity: normal
> Tags: patch upstream
> 
> This report will mostly be a duplicate of #74087, closed almost 13 years
> ago, without any explanation that I can find in the bug log, and without
> actually fixing it as far as I can tell from the packages from that era
> on archive.debian.org.
> 
> The problem now is as it was then: djpeg can't handle all jpegs. The
> ones it doesn't handle are the ones encoded as YCCK or CMYK. The bug log
> for #74087 doesn't mention YCCK or CMYK, so it's possible that the
> problem just wasn't understood back then. But the sample included in the
> original bug report is a YCCK jpeg.

Yes this is my fault. I closed it because it was not Debian specific in
anyway, so I assumed the JPEG image was invalid.

> This time, there's a patch. The patch has been seen before too, in a
> slightly different form, targeted at libjpeg-turbo. It adds a couple of
> conversion functions to the library, allowing clients like djpeg to get
> RGB output regardless of the input.
> 
>   http://sourceforge.net/p/libjpeg-turbo/patches/15/
> 
> It was rejected there, but I hope history won't repeat itself here.
> It makes no sense that djpeg (the Decode JPEG program from the de facto
> JPEG reference implementation!) can't decode all jpegs. The people in
> the libjpeg-turbo discussion didn't even seem to realize they were
> deciding to keep their version of djpeg crippled forever.
> 
> The conversion code could be moved into djpeg, leaving the library
> untouched, but djpeg isn't the only place something like this is needed.
> I'd also like to see xli not choke on these jpegs.
> 
> If the conversion is supported by the library, then adding YCCK-jpeg
> support to djpeg and xli is a 3-line patch for each program. 
> 
> If the conversion function is banned from the library like the
> libjpeg-turbo people seem to want, xli and djpeg both need the same big
> mess of pixel-shuffling code inserted into them, and so will the next
> program. That's just a stupid way to do it.

Dear Alan, I have forwarded your bug report to the upstream maintainer.
Thanks for taking the time to work on this.

However, I have a question: how do you generate such JPEG images ?
Would there be benefit for libjpeg to be able to do that ?

Cheers,
-- 
Bill. <ballo...@debian.org>

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to