transliterate

Transliteration engine
git clone git://lumidify.org/transliterate.git
Log | Files | Refs | README | LICENSE

commit 3c4e5e3eeec87344d77e63d0eeaff048f58f499f
parent 103e3fb6c16c4681a3553959349e7888d77961f6
Author: lumidify <nobody@lumidify.org>
Date:   Wed,  1 Apr 2020 18:00:32 +0200

Fix documentation formatting

Diffstat:
Mtransliterate.pl | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/transliterate.pl b/transliterate.pl @@ -1783,7 +1783,7 @@ will be prompted to choose one of the options during the transliteration process If, for whatever reason, the same table is needed twice, but with different endings, the table can simply be loaded twice with different IDs. If the same path is loaded, the table that has already been loaded will be reused. Note that this feature was -added before adding C<revert>, so the old table is used even if it had C<revert> +added before adding B<revert>, so the old table is used even if it had B<revert> set and the new one doesn't. This is technically a problem, but I don't know of any real-world case where it would be a problem, so I'm too lazy to change it. Tell me if it actually becomes a problem for you.