Your message dated Mon, 10 Oct 2016 08:34:08 +0200
with message-id
<CA+7wUsy6fWpp8KMKwiroxkoOd2wt8UMv=ryXwHjP=ptL+=TS=g...@mail.gmail.com>
and subject line CharLS: One JPEG-LS not handled
has caused the Debian Bug report #824818,
regarding CharLS: One JPEG-LS not handled
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
824818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824818
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:charls
Version: 1.0-7
I recently discover that at least one instance of a JPEG-LS codestream
is not handled by CharLS:
http://gdcm.sourceforge.net/thingies/JPEG_LS_InvalidEscapeSequence_COM_padding.dcm
I've tried to simplify it:
- Remove COM marker,
- Change the recommended DICOM padding with a simplier mechanism (a traliing 0)
but CharLS still reject that file again:
http://gdcm.sourceforge.net/thingies/JPEG_LS_InvalidEscapeSequence.dcm
I've not tested yet with 1.1.0 or 2.0.0 yet.
--- End Message ---
--- Begin Message ---
tags 824818 wontfix
thanks
Not much can be done, since this is an issue in the JPEG-LS codestream
itself. See fixed version at:
http://gdcm.sourceforge.net/thingies/JPEG_LS_InvalidEscapeSequence_Correct.dcm
--- End Message ---
