Make ISO_IR 6 value for SpecificCharacterEncoding not console.warn() about an unsupported encoding.
If the SpecificCharacterEncoding in a DICOM isn't supported by Node.js'TextDecoder then the error is now propagated and reading the DICOM will fail. The reason is that swallowing errors from unsupported encodings and proceeding seems like a dangerous/undesirable thing to do.
Upon closer inspection there were some bigger problems with character set handling which are addressed in #299. Am closing this PR in favour of that one.
This PR makes two changes:
ISO_IR 6
value forSpecificCharacterEncoding
notconsole.warn()
about an unsupported encoding.SpecificCharacterEncoding
in a DICOM isn't supported by Node.js'TextDecoder
then the error is now propagated and reading the DICOM will fail. The reason is that swallowing errors from unsupported encodings and proceeding seems like a dangerous/undesirable thing to do.