# HG changeset patch
# User Sebastien Jodogne <s.jodogne@gmail.com>
# Date 1619625724 -7200
# Node ID 566f0af3e4ed0e3d13fa263d16e96f823a4cfa23
# Parent  55a93745e87444b44ab484e2bd2a713d9fa90d13
dicom-sr

diff -r 55a93745e874 -r 566f0af3e4ed Sphinx/source/faq/supported-images.rst
--- a/Sphinx/source/faq/supported-images.rst	Wed Apr 28 16:16:33 2021 +0200
+++ b/Sphinx/source/faq/supported-images.rst	Wed Apr 28 18:02:04 2021 +0200
@@ -10,13 +10,19 @@
 <configuration>` can be set to `true` if interfacing with modalities
 that are producing non-standard SOP classes.
 
-Orthanc Explorer can **display the raw DICOM tags** of any such DICOM
-file (including notably DICOM-SR structured reports).
+Orthanc Explorer can also **display the raw DICOM tags** of any such
+DICOM file.
 
-However, the core engine of Orthanc is not able to **render all of the
-DICOM files as PNG images**. An image that Orthanc cannot decode is
-displayed as "Unsupported" by clicking on the "Preview" buttons of
-Orthanc Explorer. Currently, the core engine of Orthanc can decode:
+For instance, **DICOM-SR and DICOM-RT** instances are supported by
+Orthanc, i.e. such file can be received/stored/retransmitted with
+Orthanc. However, if you need to analyze/create such files, you will
+have to resort on another specialized tool.
+
+As far as pixel data is concerned, the core engine of Orthanc is **not
+able to render all of the DICOM instances as PNG images**. An image
+that Orthanc cannot decode is displayed as "Unsupported" by clicking
+on the "Preview" buttons of Orthanc Explorer. Currently, the core
+engine of Orthanc can decode:
 
 * uncompressed (raw) DICOM files,
 * JPEG DICOM files, and
@@ -25,7 +31,8 @@
 The supported photometric interpretations are:
 
 * RGB,
-* Grayscale2.
+* Grayscale2,
+* YUV if dealing with JPEG derivatives.
 
 The Orthanc core supports from 8bpp to 16bpp depth, with integer
 values.  Multiframe (notably cine), uncompressed DICOM instances can