MITAB: Update doc about UTF-8 encoding and STRICT_FIELDS_NAME_LAUNDER…

…ING option
drons · Jun 28, 2024 · a02dab3 · a02dab3
1 parent 102100d
commit a02dab3
Show file tree

Hide file tree

Showing 2 changed files with 17 additions and 0 deletions.
diff --git a/doc/source/drivers/vector/mapinfo_encodings.csv b/doc/source/drivers/vector/mapinfo_encodings.csv
@@ -1,5 +1,6 @@
 "ENCODING value","MapInfo charset",description
 """"" (empty string)",Neutral,"No character conversions performed."
+"UTF-8","UTF-8","UTF-8 (Works with recent MapInfo versions, since v15.2)"
 "ISO-8859-1","ISO8859_1","ISO 8859-1 (UNIX)"
 "ISO-8859-2","ISO8859_2","ISO 8859-2 (UNIX)"
 "ISO-8859-3","ISO8859_3","ISO 8859-3 (UNIX)"

diff --git a/doc/source/drivers/vector/mitab.rst b/doc/source/drivers/vector/mitab.rst
@@ -131,6 +131,14 @@ The following dataset creation options are supported:
       bytes. Any MapInfo version should be able to handle block sizes from
       512 to 32256.
 
+-  .. dsco:: STRICT_FIELDS_NAME_LAUNDERING
+      :choices: YES, NO
+      :default: YES
+      :since: 3.10
+
+      Replaces all non alphanumeric characters in dataset's field names by
+      `_` (underscope). For recent MapInfo can be set to `NO`.
+
 Layer Creation Options
 ~~~~~~~~~~~~~~~~~~~~~~
 
@@ -166,6 +174,14 @@ The following layer creation options are supported:
       TAB format). Friendly names can be up to 256 characters long and can include
       most ASCII characters. Supported by MapInfo Pro v15.0 or higher.
 
+-  .. lco:: STRICT_FIELDS_NAME_LAUNDERING
+      :choices: YES, NO
+      :default: YES
+      :since: 3.10
+
+      Replaces all non alphanumeric characters in layer's field names by
+      `_` (underscope). For recent MapInfo can be set to `NO`.
+
 Configuration options
 ~~~~~~~~~~~~~~~~~~~~~