[Debian-med-packaging] Bug#988644: Defined Term: ISO 2022 IR 87 is not supported

Mathieu Malaterre malat at debian.org
Mon May 17 13:52:39 BST 2021


Hi Jörg !

On Mon, May 17, 2021 at 2:18 PM Jörg Riesmeier <debian at riesmeier.de> wrote:
>
> I can confirm that DCMTK with ICU enabled does not support the same set of
> DICOM character sets (i.e. all) in contrast to the original implementation
> based on libiconv. That's the reason why I personally would still prefer
> libiconv over the other two character set options in DCMTK.
>
> By the way, this is a well-known issue for the character set conversion
> support of DCMTK. I hope that the author of the ICU and stdlibc (iconv)
> support will fix it anytime soon.

Could you please clarify the following statement then:

[...]
As far as I understand it ISO 2022 JP is also a set containing
multiple character sets that can be switched via escape sequences. The
ICU handles these escape sequences internally whereas the libiconv
doesn't. This is why the existing code in DCMTK that was orignally
written for libiconv parses these escape sequences itself, therefore,
the ICU does not perceive them and cannot chose the correct character
set. The only way to fix this would be to disable parsing the escape
sequences when the ICU is used and then set all character sets similar
to your proposition.
[...]

Thanks,

ref:
* https://forum.dcmtk.org/viewtopic.php?p=18480&sid=c3f13bb9c9ae0e54bef6276a5d337980#p18480



More information about the Debian-med-packaging mailing list