I think I am finished with syncing with https://github.com/indic-transliteration/m17n-db-indic

[Mike FABIAN]

Hi Vishvas,

I think I am finished syncing with the stuff you have in
https://github.com/indic-transliteration/m17n-db-indic

I pushed what I currently have to this release-candidate-1-8-4 branch:

https://git.savannah.nongnu.org/cgit/m17n/m17n-db.git/log/?h=release-candidate-1-8-4

There is one remaining difference to
https://github.com/indic-transliteration/m17n-db-indic :

--- MIM/global.mim      2023-08-05 16:20:00.754091849 +0200
+++ /local/mfabian/src/m17n-db-indic/global.mim 2023-08-11 18:07:57.514691897 
+0200
@@ -53,7 +53,7 @@
 when you type \"/...\" while you are activating an input method
 that doesn't handle that key sequence, \"lsymbol\" input method is activated
 and \"…\" (U+2026: HORIZONTAL ELLIPSIS) is inserted.")
-  "lsymbol, unicode"))
+  "lsymbol, ssymbol, math-latex, unicode"))

 (command
  (commit


I am unsure about that one. I think I would rather leave the default as
only "lsymbol, unicode". "unicode" did already annoy some people, see
this thread:

https://lists.nongnu.org/archive/html/m17n-list/2023-02/msg00000.html

math-latex.mim uses \ as a starter. This might already surprise users of
input methods which do not handle \ if they suddenly get mathematical
symbols by typing \ + some string.

ssymbol.mim seems even worse, it does not use a starter at all and it
would really be surprising if ">>" suddenly changes into "→" just
because the currently used input method does not handle > and ssymbol is
used as a fallback.

To avoid such surprises, I think it is better to leave the default as
only "lsymbol, unicode".

-- 
Mike FABIAN <mfabian@redhat.com>
睡眠不足はいい仕事の敵だ。