Re: Problem in hi-itrans or not?

[Vishvas Vasuki]

Those are rarely used characters - while we have (phonetic intuitionwise) superior alternatives (ea, oa), there's no harm in following the "standard" ITRANS maps. PS - https://github.com/indic-transliteration/m17n-db-indic/commit/592d832d06f07b2c21d46dcb41b76a9744ce260c  (fixed the oa map along the way - tested only with sa-vedic-itrans, which I use all the time.)

On Thu, 5 Sept 2024 at 20:23, Mike FABIAN <mfabian@redhat.com> wrote:

Somebody reported an issue against ibus-m17n while trying to use hi-itrans:

https://github.com/ibus/ibus-m17n/issues/85

What he observes has nothing to do with ibus-m17n though, it is the
normal behaviour of hi-itrans. He writes:

> According to the ITRANS unicode table
> (https://www.aczoom.com/itrans/online/itrans6/itrans-tables-unicode.pdf)
> and documentation (https://www.aczoom.com/itrans/html/dvnc/node3.html),
> the key combination .c is supposed to modify the character preceding it
> it (e.g. ka.c -> कॅ , aa.c -> ऑ ), however when I try this, I get कऍ and
> आऍ respectively. Inputting .c thus returns ऍ , rather than modifying the
> previous character.
>
> To Reproduce
> Steps to reproduce the behavior:
>
>     Click on ibus tray icon.
>     Click on 'Hindi - hi-itrans (m17n)'.
>     Type 'aa.c' on US-style keyboard.
>     See it return 'आऍ'.
>
> Expected behavior
> I expected input 'aa.c' to return 'ऑ'.

With hi-itrans (and also with mr-itrans and mr-gamabhana) one can do this:

To get कॅ you can type k.c instead of ka.c.
To get ऑ you can type o.c instead of aa.c.

But the link he gave
(https://www.aczoom.com/itrans/online/itrans6/itrans-tables-unicode.pdf)
mentions "ka.c कॅ".

So I wonder whether there is a problem in hi-itrans or not. Is the table
at the link
https://www.aczoom.com/itrans/online/itrans6/itrans-tables-unicode.pdf
relevant? Is it up-to-date?

Or maybe hi-itrans is fine as it is now ...


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

--

--
Vishvas /विश्वासः