add warning about experimental nature of ICU tokenizer

diff --git a/docs/admin/Tokenizers.md b/docs/admin/Tokenizers.md
index a4d6aa0d247d2c01778722db158398f86c0483b4..782d50b873fe4ce166e48678b41ac9522403dc03 100644 (file)
--- a/docs/admin/Tokenizers.md
+++ b/docs/admin/Tokenizers.md
@@ -9,11 +9,11 @@ different configuration options. This sections describes the tokenizers and how
 they can be configured.
 
 !!! important
 they can be configured.
 
 !!! important

-The use of a tokenizer is tied to a database installation. You need to choose
-and configure the tokenizer before starting the initial import. Once the import
-is done, you cannot switch to another tokenizer anymore. Reconfiguring the
-chosen tokenizer is very limited as well. See the comments in each tokenizer
-section.
+    The use of a tokenizer is tied to a database installation. You need to choose
+    and configure the tokenizer before starting the initial import. Once the import
+    is done, you cannot switch to another tokenizer anymore. Reconfiguring the
+    chosen tokenizer is very limited as well. See the comments in each tokenizer
+    section.

 
 ## Legacy tokenizer
 
 
 ## Legacy tokenizer
 


@@ -44,6 +44,10 @@ normalization functions are hard-coded.
 
 ## ICU tokenizer
 
 
 ## ICU tokenizer
 

+!!! danger
+    This tokenizer is currently in active development and still subject
+    to backwards-incompatible changes.
+

 The ICU tokenizer uses the [ICU library](http://site.icu-project.org/) to
 normalize names and queries. It also offers configurable decomposition and
 abbreviation handling.
 The ICU tokenizer uses the [ICU library](http://site.icu-project.org/) to
 normalize names and queries. It also offers configurable decomposition and
 abbreviation handling.