Closed GoogleCodeExporter closed 9 years ago
Strictly speaking, the file you have sent is not encoded using Cyrillic as
understood by the DICOM standard (i.e. using the "ISO_IR 144" specific
character set). The "SpecificCharacterSet" (0x0008,0x0005) is incidentally
absent.
Instead, the strings are encoded using the "Windows 1251" codepage, that is in
practice more common than Cyrillic (but that is not officially supported by
DICOM):
http://en.wikipedia.org/wiki/Windows-1251
To overcome your problem, the mainline of Orthanc now allows to set the
"Windows1251" value in the "DefaultEncoding" option of the configuration file:
http://goo.gl/71IYKM
If this option is set and Orthanc encounters a file without
SpecificCharacterSet, Orthanc will assume that it is encoded using the Windows
1251 codepage. The strings are then properly reported:
# curl
http://localhost:8042/instances/49a8037a-95d3e0a8-27b9c17b-d7687a5f-05d3a2eb/tag
s?simplify
{
"BodyPartExamined" : "Таз",
"PerformedProcedureStepDescription" : "Рентгенография",
"SeriesDescription" : "Рентгенография",
"ViewPosition" : "Прямая",
[...]
}
This patch will be part of Orthanc 0.8.7.
Original comment by s.jodo...@gmail.com
on 21 Apr 2015 at 3:56
BTW, I have just pushed a debug, experimental version of Orthanc with this
Cyrillic support on SourceForge:
https://sourceforge.net/projects/orthancserver/files/DevelopmentSnapshots/
Any feedback is welcome :)
Thanks for providing us with this DICOM file!
Sébastien-
Original comment by s.jodo...@gmail.com
on 22 Apr 2015 at 1:55
Thanks a lot!
But at this experimental version i can't see the setings file. Where I can find
it and change encoding to Windows1251?
Because at defaults look like Latin1
when is expected to release a new version?
Original comment by aceber...@gmail.com
on 29 Apr 2015 at 1:49
The creation of a setting file is explained here:
https://code.google.com/p/orthanc/wiki/OrthancConfiguration
Original comment by s.jodo...@gmail.com
on 29 Apr 2015 at 5:41
finally I got to run the Cyrillic version. It works great. Now we are waiting
for the release.
Original comment by aceber...@gmail.com
on 30 Apr 2015 at 12:04
Original issue reported on code.google.com by
aceber...@gmail.com
on 20 Apr 2015 at 11:43