Bug#675448: dcmtk: dcmdjpeg does not set (0028, 2114) LossyImageCompressionMethod when decompressing lossy compressed DICOM file

2021-11-19 Thread Mathieu Malaterre
Control: fixed -1 3.6.2-1 Control: forwarded -1 http://support.dcmtk.org/redmine/issues/307 According to upstream, this bug is solved: % git show --oneline 23720ba2c1b81d65924f8088308bd4dae594643b | head -1 23720ba2c Now setting LossyImageCompression when decompressing. % git tag --contains 23720

Bug#675448: dcmtk: dcmdjpeg does not set (0028, 2114) LossyImageCompressionMethod when decompressing lossy compressed DICOM file

2018-03-09 Thread Michael Onken
On Fri, 1 Jun 2012 15:05:46 +0200 Mathieu Malaterre wrote: > On Fri, Jun 1, 2012 at 2:46 PM, OFFIS DICOM Team wrote: > > Anyway, we already have a corresponding entry (#307) in our internal list of > > things to do - this one has been added about 3 years ago. Thanks for the > > reminder! This h

Bug#675448: dcmtk: dcmdjpeg does not set (0028, 2114) LossyImageCompressionMethod when decompressing lossy compressed DICOM file

2012-06-01 Thread Mathieu Malaterre
tags 675448 confirmed tags 675448 upstream thanks On Fri, Jun 1, 2012 at 2:46 PM, OFFIS DICOM Team wrote: > Hi Mathieu, > >> dcmdjpeg does not currently properly support lossy compressed DICOM file. >> It decompress them as lossless file, lossing the lossy information from >> the original file. E

Bug#675448: dcmtk: dcmdjpeg does not set (0028, 2114) LossyImageCompressionMethod when decompressing lossy compressed DICOM file

2012-06-01 Thread Mathieu Malaterre
Package: dcmtk Version: 3.6.0-10 Severity: important dcmdjpeg does not currently properly support lossy compressed DICOM file. It decompress them as lossless file, lossing the lossy information from the original file. Eg: $ dcmdjpeg DCMTK_JPEGExt_12Bits.dcm lossless.dcm $ dcmdump lossless.dcm