# HG changeset patch
# User Sebastien Jodogne <s.jodogne@gmail.com>
# Date 1717594977 -7200
# Node ID 53ddff5dccaf9a9f16cb271e8eb3f50ba01448d7
# Parent  c4e33e0f907b23fd4f883ff444a4eb5ecab30cb2
revisiting NEWS

diff -r c4e33e0f907b -r 53ddff5dccaf NEWS
--- a/NEWS	Wed Jun 05 11:04:37 2024 +0200
+++ b/NEWS	Wed Jun 05 15:42:57 2024 +0200
@@ -9,26 +9,24 @@
 * Added a new "LimitToThisLevelMainDicomTags" field in the payload of 
   /patients|studies|series/instances/../reconstruct to speed up the reconstruction
   in case you just want to update the MainDicomTags of that resource level only 
-  e.g. after you have updated the 'ExtraMainDicomTags' for this level.
-* The "requestedTags" GET argument was deprecated in favor of "requested-tags".
-* Fixed broken /instances/../tags route after the calling
-  /studies/../reconstruct when changing the "IngestTranscoding".
-* Added "?whole" option to "/instances/{id}/tags" to access tags stored after pixel data.
+  (e.g., after you have updated the "ExtraMainDicomTags" for this level)
+* The "requestedTags" GET argument is deprecated in favor of "requested-tags"
+* Added "?whole" option to "/instances/{id}/tags" to access tags stored after pixel data
 
 Plugins
 -------
 
-* Multitenant DICOM plugin: added support for locales
+* Multitenant DICOM plugin: added support for locales.
 * Housekeeper plugin: 
   - Added an option "LimitMainDicomTagsReconstructLevel"
-    (allowed values: "Patient", "Study", "Series", "Instance").  This can greatly speed
-    up the housekeeper process e.g. if you have only update the Study level ExtraMainDicomTags.
+    (allowed values: "Patient", "Study", "Series", "Instance"). This can greatly speed
+    up the housekeeper process, e.g. if you have only update the Study level ExtraMainDicomTags.
   - Fixed broken /instances/../tags route after running the Housekeeper
-    after having changed the "IngestTranscoding". 
-* SDK: added OrthancPluginLogMessage() that is a new primitive for
-  plugins to log messages.  This new primitive will display the plugin
-  name, the plugin file name, and the plugin line number in the
-  logs. If they are not using the LOG() facilities provided by the
+    after having changed the "IngestTranscoding".
+* SDK: added OrthancPluginLogMessage() as a new primitive for plugins
+  to log messages. This new primitive will display the plugin name,
+  the plugin file name, and the plugin line number in the logs. If
+  they are not using the LOG() facilities provided by the
   OrthancFramework, plugins should now use ORTHANC_PLUGINS_LOG_INFO(),
   ORTHANC_PLUGINS_LOG_WARNING(), and ORTHANC_PLUGINS_LOG_ERROR().
 
@@ -36,13 +34,13 @@
 -----------
 
 * C-Find queries:
-  - In C-Find queries including GenericGroupLength tags, Orthanc was still
+  - In C-Find queries including "GenericGroupLength" tags, Orthanc was still
     extracting these tags from the storage although they were already ignored
     and not returned in the response.
     They are now removed from the query earlier to avoid this disk access that
-    could slow down the response time.  Note that this seems to happen mainly
+    could slow down the response time. Note that this seems to happen mainly
     when the query originates from some GE devices (AWS).
-  - TimezoneOffsetFromUTC is now ignored for matching.
+  - "TimezoneOffsetFromUTC" is now ignored for matching.
 * The 0x0111 DIMSE Status is now considered as a warning instead of an error
   when received as a response to a C-Store.
   See https://discourse.orthanc-server.org/t/ignore-dimse-status-0x0111-when-sending-partial-duplicate-studies/4555/3
@@ -52,16 +50,18 @@
   resource type, not only the resource identifier identifier.
 * DICOM TLS:
   - In prior versions, when "DicomTlsRemoteCertificateRequired" was set to false, Orthanc
-    was still sending a client certificate request during the TLS handshake but was not triggering
-    and error if the client certificate was not trusted (equivalent to the --verify-peer-cert DCMTK option)
-    From this version, if this option is set to false, Orthanc will not send a 
-    client certificate request during the TLS handshake anymore (equivalent to the --ignore-peer-cert 
-    DCMTK option).
+    was still sending a client certificate request during the TLS handshake but was not
+    triggering and error if the client certificate was not trusted (equivalent to the
+    "--verify-peer-cert" DCMTK option). Starting with Orthanc 1.12.4, if this option is
+    set to "false", Orthanc will not send a client certificate request during the TLS
+    handshake anymore (equivalent to the "--ignore-peer-cert" DCMTK option).
   - When working with "DicomTlsEnabled": true and "DicomTlsRemoteCertificateRequired": false,
     Orthanc was refusing to start if no "DicomTlsTrustedCertificates" was provided.
-  - New configurations:
+  - New configuration options:
     - "DicomTlsMinimumProtocolVersion" to select the minimum TLS protocol version
     - "DicomTlsCiphersAccepted" to fine tune the list of accepted ciphers
+* Fixed broken /instances/../tags route after calling of
+  /studies/../reconstruct after having changed the "IngestTranscoding".
 * Upgraded dependencies for static builds:
   - boost 1.85.0