From 1a7d56df56b4f93b539117c4f76c566da0f6e019 Mon Sep 17 00:00:00 2001
From: albert-github <albert.tests@gmail.com>
Date: Mon, 2 Nov 2020 14:16:02 +0100
Subject: Documentation correction for CASE_SENSE_NAMES

In issue #8129 the problem of using different case of filenames was addressed, though in the documentation it was not clear what this meant for input files.
This has been corrected (the underlying problem has been handled with different other commits a.o. 2b5a4541fb6f806c02a1f6e65a1ff2610f29751f ).
---
 src/config.xml | 17 +++++++++++------
 1 file changed, 11 insertions(+), 6 deletions(-)

diff --git a/src/config.xml b/src/config.xml
index b080bec..a97ab53 100644
--- a/src/config.xml
+++ b/src/config.xml
@@ -981,12 +981,17 @@ Go to the <a href="commands.html">next</a> section or return to the
     <option type='bool' id='CASE_SENSE_NAMES' defval='0' altdefval='Portable::fileSystemIsCaseSensitive()'>
       <docs>
 <![CDATA[
- If the \c CASE_SENSE_NAMES tag is set to \c NO then doxygen
- will only generate file names in lower-case letters. If set to
- \c YES, upper-case letters are also allowed. This is useful if you have
- classes or files whose names only differ in case and if your file system
- supports case sensitive file names. Windows (including Cygwin) and
- Mac users are advised to set this option to \c NO.
+ With \c CASE_SENSE_NAMES doxygen will be better able to match the
+ capabilities of the underlying file system.
+ In case the files system supports files whose name only differs in the
+ case used, the option must be set to \c YES to properly deal with such input files
+ if they appear in the input, whereas for file systems that are not case
+ sensitive the option should be be set to \c NO to properly deal with output files
+ for symbols that only differ in case, like two classes one named \c CLASS
+ and the other named \c Class and to support references to files without
+ having to specify the correct case.
+
+ On Windows (including Cygwin) and Mac users are advised to set this option to \c NO.
 ]]>
       </docs>
     </option>
-- 
cgit v0.12


From 9bbd3f5b9b63133e925c30e8acb7615fdbe8c297 Mon Sep 17 00:00:00 2001
From: Dimitri van Heesch <doxygen@gmail.com>
Date: Mon, 2 Nov 2020 20:02:45 +0100
Subject: Update config.xml

Did rephrasing things a bit.
---
 src/config.xml | 23 +++++++++++++----------
 1 file changed, 13 insertions(+), 10 deletions(-)

diff --git a/src/config.xml b/src/config.xml
index a97ab53..82e2afe 100644
--- a/src/config.xml
+++ b/src/config.xml
@@ -981,17 +981,20 @@ Go to the <a href="commands.html">next</a> section or return to the
     <option type='bool' id='CASE_SENSE_NAMES' defval='0' altdefval='Portable::fileSystemIsCaseSensitive()'>
       <docs>
 <![CDATA[
- With \c CASE_SENSE_NAMES doxygen will be better able to match the
- capabilities of the underlying file system.
- In case the files system supports files whose name only differs in the
- case used, the option must be set to \c YES to properly deal with such input files
- if they appear in the input, whereas for file systems that are not case
- sensitive the option should be be set to \c NO to properly deal with output files
- for symbols that only differ in case, like two classes one named \c CLASS
- and the other named \c Class and to support references to files without
- having to specify the correct case.
+ With the correct setting of option \c CASE_SENSE_NAMES doxygen will better be able to match the
+ capabilities of the underlying filesystem. 
 
- On Windows (including Cygwin) and Mac users are advised to set this option to \c NO.
+ In case the filesystem is case sensitive (i.e. it supports files in the same directory 
+ whose names only differ in casing), the option must be set to \c YES to properly deal with such files
+ in case they appear in the input. 
+ 
+ For filesystems that are not case sensitive the option should be be set to \c NO to properly 
+ deal with output files written for symbols that only differ in casing, such as for two classes, 
+ one named \c CLASS and the other named \c Class, and to also support references to files without
+ having to specify the exact matching casing.
+
+ On Windows (including Cygwin) and MacOS, users should typically set this option to \c NO,
+ whereas on Linux or other Unix flavors it should typically set to \c YES.
 ]]>
       </docs>
     </option>
-- 
cgit v0.12


From a29a2efd84101509aaebc61ecfa9139a45fb5e15 Mon Sep 17 00:00:00 2001
From: Dimitri van Heesch <doxygen@gmail.com>
Date: Mon, 2 Nov 2020 20:28:55 +0100
Subject: Update config.xml

added missing "be"
---
 src/config.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/config.xml b/src/config.xml
index 82e2afe..861b3c6 100644
--- a/src/config.xml
+++ b/src/config.xml
@@ -994,7 +994,7 @@ Go to the <a href="commands.html">next</a> section or return to the
  having to specify the exact matching casing.
 
  On Windows (including Cygwin) and MacOS, users should typically set this option to \c NO,
- whereas on Linux or other Unix flavors it should typically set to \c YES.
+ whereas on Linux or other Unix flavors it should typically be set to \c YES.
 ]]>
       </docs>
     </option>
-- 
cgit v0.12