tAdd clarification to documentation - transliterate - Transliteration engine
HTML git clone git://lumidify.org/transliterate.git
DIR Log
DIR Files
DIR Refs
DIR README
DIR LICENSE
---
DIR commit cfe056c927013689acb20a150d70d66655026dd4
DIR parent 6990df581565ad3aba6d1a73578ae10c210f805d
HTML Author: lumidify <nobody@lumidify.org>
Date: Fri, 17 Apr 2020 14:26:20 +0200
Add clarification to documentation
Diffstat:
M transliterate.pl | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
---
DIR diff --git a/transliterate.pl b/transliterate.pl
t@@ -2058,7 +2058,9 @@ B<override> can be useful if the same database is used for both directions and
one direction maps multiple words to one word, but in the other direction this
word should always default to one of the choices. In that case, a small table
with these special cases can be created and put at the end of the main B<group>
-statement with B<override> set.
+statement with B<override> set. This is technically redundant since you could
+just add a special group with only the override table in it earlier in the
+config, but it somehow seems cleaner this way.
Note that a table must have been loaded before being used in a B<replace> statement.