Code Extension

178 views
Skip to first unread message

Mariusz Kowalski

unread,
Jul 10, 2015, 7:14:01 AM7/10/15
to fo-d...@googlegroups.com
Hi,

I need to test some DICOM files with Japanese characters where code extension is used.
Is fo-dicom doesn't support such cases or do I do something wrong?

I've attached some sample file:
Specific Character Set (0008,0005) \ISO 2022 IR 13\ISO 2022 IR 87

When I open it with DICOM Dump tags where Japanese characters are used are wrong:
Patient's Name, Patient ID, Patient Comments, Additional Patient History

How can I fix it myself or maybe it will be fixed with next release?

Thanks,
Mariusz
sample.dcm

Anders Gustafsson Cureos AB

unread,
Jul 13, 2015, 5:26:04 AM7/13/15
to fo-d...@googlegroups.com
Many thanks for reporting this issue. I have created a Github issue #43 here. It would be great if we could continue the discussion on this topic on Github.

Best regards,
Anders @ Cureos

Anders Gustafsson Cureos AB

unread,
Jul 23, 2015, 8:16:51 AM7/23/15
to Fellow Oak DICOM for .NET, cure...@gmail.com
Mariusz,

I have published an update on the Github Issues page, please have a look here: https://github.com/fo-dicom/fo-dicom/issues/43

Regards,
Anders @ Cureos
Message has been deleted

Mariusz Kowalski

unread,
Jul 27, 2015, 5:25:55 AM7/27/15
to Fellow Oak DICOM for .NET, cure...@gmail.com
Anders,

Thank you for dealing with this issue.

I think that using backslash at the beginning of Specific Character Set  is correct. I search a little and here are some examples:

I think that it is wrong behavior that fo-dicom uses only one (first) encoding because (if I understand this mechanism clearly) in case of Code Extension there are some escape characters in strings which should invoke switching of encoding.

Next thing is that when i remove backslash from the beginning of Specific Character Set fo-dicom still display some of tags incorrect:


Thanks,
Mariusz

Anders Gustafsson Cureos AB

unread,
Jul 27, 2015, 1:30:16 PM7/27/15
to Fellow Oak DICOM for .NET, kowalski....@gmail.com
Many thanks for those links, Mariusz. You are right, I stand corrected :-)

Currently, fo-dicom does not support code extension techniques, but of course it should. I will post a Github issue regarding this. As far as I can tell, it is quite a large task to implement though, so it will have to wait until after the version 1.1.0 of fo-dicom that we are about to release shortly.

As an additional help, Mariusz, could you please also display the correct values of the tags above?

Best regards,
Anders

PS. For reference, I will twin-post yours and my response on Github. I hope you don't mind. It would also simplify future reference for the development if you could post subsequent responses on Github. Thanks in advance!

Mariusz Kowalski

unread,
Jul 28, 2015, 1:54:20 AM7/28/15
to Fellow Oak DICOM for .NET, cure...@gmail.com
Correct values:

Patient's Name: ??^??=漢字^表意=かな^ひょうおん
Patient ID: @DM_Cod11_マダタロウ
Patient Comments: YamadaTarou山田太郎ヤマダタロウ
Additional Patient History: YamadaTarou山田太郎ヤマダタロウ

Thanks for your effort, Anders.

Regards,
Mariusz
Reply all
Reply to author
Forward
0 new messages