tFix documentation - transliterate - Transliteration engine
HTML git clone git://lumidify.org/transliterate.git
DIR Log
DIR Files
DIR Refs
DIR README
DIR LICENSE
---
DIR commit fc07368bf87636971eca205be8a3ab50e9084e13
DIR parent 975878ae4986069b28835251e86f7a74f94e76aa
HTML Author: lumidify <nobody@lumidify.org>
Date: Sun, 24 May 2020 09:31:37 +0200
Fix documentation
Diffstat:
M README | 6 ++++++
M transliterate.pl | 4 ++--
2 files changed, 8 insertions(+), 2 deletions(-)
---
DIR diff --git a/README b/README
t@@ -1,5 +1,11 @@
See the perldoc in transliterate.pl for documentation (run perldoc -F transliterate.pl).
+Alternatively, the most recent documentation is available at the following locations:
+http://lumidify.org/doc/transliterate.html
+https://lumidify.org/doc/transliterate.html
+gopher://lumidify.org/0/doc/transliterate.txt
+gopher://uaeoa3mvlc4vgjlv.onion/0/doc/transliterate.txt
+
REQUIREMENTS: gtk2-perl
See the repository "transliterate_data" for a real-world configuration.
DIR diff --git a/transliterate.pl b/transliterate.pl
t@@ -1792,8 +1792,8 @@ This section was added to explain to the user how the transliteration
process works internally since that may be necessary to understand
why certain words are replaced the way they are.
-First off, the process works line-by-line, i.e. no B<match> statement
-will ever match anything that crosses the end of a line.
+First off, the process works line-by-line, i.e. no B<match> or B<replace>
+statement will ever match anything that crosses the end of a line.
Each line is initially stored as one chunk which is marked as
untransliterated. Then, all B<match>, B<matchignore>, and B<replace>