-
Notifications
You must be signed in to change notification settings - Fork 636
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specific character set doesn't not comply with standards #1624
Labels
Comments
Thank you - that is indeed a bug in |
mrbean-bremen
added a commit
to mrbean-bremen/fo-dicom
that referenced
this issue
Jul 6, 2023
* single value encodings have been returned as "ISO IR ###" instead of "ISO_IR ###" * Tolerate Specific Character Set values misspelled as "ISO-IR ###" additionally to "ISO IR ###" * fixes fo-dicom#1624
5 tasks
mrbean-bremen
added a commit
to mrbean-bremen/fo-dicom
that referenced
this issue
Jul 10, 2023
* single value encodings have been returned as "ISO IR ###" instead of "ISO_IR ###" * Tolerate Specific Character Set values misspelled as "ISO-IR ###" additionally to "ISO IR ###" * fixes fo-dicom#1624
gofal
pushed a commit
that referenced
this issue
Jul 13, 2023
* single value encodings have been returned as "ISO IR ###" instead of "ISO_IR ###" * Tolerate Specific Character Set values misspelled as "ISO-IR ###" additionally to "ISO IR ###" * fixes #1624 Co-authored-by: Alexander Moerman <alexander.moerman@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
DicomEncoding.GetCharset returns ISO IR 192 for utf-8 and should instead return ISO_IR 192.
To Reproduce
I send a dataset after setting the DicomTag.SpecificCharset :
The resulting encoding is ISO IR 192 instead of ISO_IR 192 in the dataset.
Expected behavior
We should have ISO_IR 192 isntead
Environment
Fellow Oak DICOM version: 5.1.1
OS: Windows 11 x64
Platform: .NET Framework 4.6.2
The text was updated successfully, but these errors were encountered: