The charset conversion code should use the DICOM charsets in order of registration
Issue #221
closed
Currently, the unicode-to-dicom charset conversion does not honor the order of registration of the charsets when selecting the most appropriate conversion table. It should honor the order of registration.
Comments (3)
-
reporter -
reporter - changed status to resolved
Resolves
#221(The charset conversion should use the DICOM charsets in order of registration) as per SOP DEVENH/2→ <<cset 822c632e10712eaf6fb4d3e6dd0440415b15937f>>
-
reporter - changed status to closed
Closed in 4.2.2.1
- Log in to comment
Addresses
#221. Updated changes log→ <<cset d4693d054db7e6f0b182acf794e5a1fede8850ea>>