[storescp] ISO_IR 101 to WIN1250

[micdob89]

Hello Everybody,

Today I noticed a potential problem when using storescp:

1. Modality device is set to use Latin 2 for communication with PACS.
2. At some point storescp is doing conversion into WIN1250(ANSI) and because of that looses six characters: ś, Ś, ą, Ą, ź, Ź which is normal when doing conversion between these two charsets.

Is there a way (other than postprocessing storescp output files) to solve that issue?

I will be very grateful for any tips how to handle that issue.

Greetings
Michal

[J. Riesmeier]

The tool storescp does not perform any character set conversion. I guess that you are referring to the console output, right?

[micdob89]

Thank you for quick reply. I assumed that the tool itself doesn't do it. On console output there aren't any national letter displayed correctly but it's normal.

The problem is that every *.wl file generated by storescp looks like converted from Latin 2 to ANSI 1250. The letters I mentioned in my first post are replaced with some symbols.

I just don't have idea where the conversion is done.

Greetings

[J. Riesmeier]

The problem is that every *.wl file generated by storescp looks like converted from Latin 2 to ANSI 1250.

The tool storescp does not generate any *.wl files. Are you talking about Modality Worklist Management?

[micdob89]

Sorry, I messed files. Doing a lot of DICOM stuff recenty...

I meant dcm files saved by storescp containing DICOM image.

[J. Riesmeier]

OK, but as I said: storescp does not do any character set conversions. So, I'd guess that the conversion (if any) is done on the sender side (or somewhere in between).

You could also check with storescp's --bit-preserving (+B) option, which makes sure that the DICOM data is written to file as received via the network association (i.e. without any "data corrections" like removal of padding or sequence/item encoding).

[micdob89]

Still nothing. It seems to me that modality device is sending corrupt files.