# HG changeset patch # User Alain Mazy # Date 1635526832 -7200 # Node ID b8171b4046da92f3a008051c9d9e5d309b08037c # Parent d050289fd0b30d3712a46a92c547cf2c972e676d fix diff -r d050289fd0b3 -r b8171b4046da Sphinx/source/faq/debugging-encodings.rst --- a/Sphinx/source/faq/debugging-encodings.rst Fri Oct 29 18:55:51 2021 +0200 +++ b/Sphinx/source/faq/debugging-encodings.rst Fri Oct 29 19:00:32 2021 +0200 @@ -13,18 +13,18 @@ If your DICOM files are valid, Orthanc should display all strings correctly both in the UI and in the Rest API in which all strings are converted to UTF-8. -However, it might still be usefull to understand what's wrong in your files +However, it might still be useful to understand what's wrong in your files such that you can possibly fix your files once they have been stored in Orthanc or configure your modality correctly. -**Example 1**: a DICOM file is sent to Orthanc with SpecificCharacterSet set to ``ISO_IR 100`` +**Example 1**: a DICOM file is sent to Orthanc with ``SpecificCharacterSet`` set to ``ISO_IR 100`` (Latin1). The PatientName is expected to be ``ccžšd^CCŽŠÐ`` but Orthanc displays ``ccžšd^CCŽŠÐ``. If you open the DICOM file in an Hex editor and search for the PatientName, you'll find this sequence of bytes: ``63 63 9e 9a 64 5e 43 43 8e 8a d0``. By checking the `Latin1 code page `__, you realise that the ``9e`` and ``9a`` characters -are not valid Latin1 characters. +are not valid Latin1 characters and are therefore replaced by ``ž`` in Orthanc UI. -In this case, they have most likely be generated on a Windows system by using the default `Windows 1252 +In this case, they have most likely been generated on a Windows system by using the default `Windows 1252 `__ encoding in which ``9e`` is ``ž``. How to solve it ? It is highly recommended to fix it before Orthanc: in your RIS, worklist server or modality.