For instance:
% curl -s --output test.dcm
"https://sourceforge.net/p/gdcm/gdcmdata/ci/master/tree/NM-PAL-16-PixRep1.dcm?format=raw";
% dcmconv +U8 test.dcm testU8.dcm
E: DcmSpecificCharacterSet: 'ISO 2022 IR 87' is not supported by the
utilized character set conversion library 'ICU, Version 63.1.0'
F: Cannot open character encoding, ICU error name:
U_FILE_ACCESS_ERROR: processing file: test.dcm
while:
% dicomdump test.dcm| grep PatientName
(0010,0010) PN "PatientName" : [テストです] (16 bytes)
With:
% apt-cache policy vtk-dicom-tools
vtk-dicom-tools:
Installed: 0.8.9-1
Candidate: 0.8.9-1
Version table:
*** 0.8.9-1 500
500 http://deb.debian.org/debian buster/main amd64 Packages
100 /var/lib/dpkg/status
On Mon, May 17, 2021 at 12:33 PM Mathieu Malaterre <ma...@debian.org> wrote:
>
> Source: dcmtk
> Version: 3.6.5-1
>
> dcmtk source package is compiled against libicu. However there is a
> false sense of support for Character Encoding. It seems the general
> support is written for libiconv specific implementation, and some
> effort has been made to support partially libicu.
>
> For reference:
>
> * https://forum.dcmtk.org/viewtopic.php?t=4566
>
> [...]
> for ex atm dcmtk/libicu generates errors on ISO 2022 IR 87/ISO 2022 IR
> 159 dicoms conversion
> [...]
>
> It would make sense to indicate that sort of information in the Debian
> package binary README file.
>
