Actions
Bug #547
closed
SR documents with extended characters (e.g. UTF-8) cannot be read
Start date:
2013-09-12
Due date:
% Done:
100%
Estimated time:
Module:
dcmsr
Operating System:
Compiler:
Description
The reason is that the VR scanner does not (yet) support extended character sets like UTF-8 (see Bug #386).
As a workaround one has to patch the dcmsr module as in the attached patch. Of course, there should be an easier way of accepting such SR documents...
David Clunie has provided the sample file "japanesecharacterset.dcm" that demonstrates the current behaviour.
Files
Updated by Jörg Riesmeier almost 12 years ago
There should be a new DSRDocument::read() flag that can be used to ignore such errors.
Updated by Jörg Riesmeier almost 12 years ago
- % Done changed from 0 to 80
Actually, the originally reported issue is closed by the following commits:
- http://git.dcmtk.org/web?p=dcmtk.git;a=commit;h=01e468ae65e42962f5dab3ee1c3efb48b2d73685
- http://git.dcmtk.org/web?p=dcmtk.git;a=commit;h=5bdebe66fdb7f566814b74022b1762a489ae55dc
However, there is still no read() flag that would allow to ignore (other) errors reported by the VR checker.
Updated by Jörg Riesmeier almost 12 years ago
- Status changed from New to Assigned
Updated by Jörg Riesmeier almost 12 years ago
- Status changed from Assigned to Closed
- % Done changed from 80 to 100
Solved by introducing a new global "dcmdata" flag: http://git.dcmtk.org/web?p=dcmtk.git;a=commit;h=06b6334cf940d9b2218937cae9c0a5b7d9a02ecc
Actions