[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: latin-prefix input method niggles
From: |
Eli Zaretskii |
Subject: |
Re: latin-prefix input method niggles |
Date: |
Thu, 10 Jan 2019 21:33:24 +0200 |
> From: Robert Pluim <address@hidden>
> Date: Thu, 10 Jan 2019 19:39:29 +0100
>
> The description of the latin-prefix input method contains
>
> cedilla | ~ | ~c -> ç
> breve | ~ | ~a -> ă
> caron | ~ | ~c -> č
> dot above | ~ / . | ~o -> ġ /o -> ġ .o -> ġ
>
> Problems:
>
> 1. the 'breve' description is inaccurate, actually ~a -> ã [1]
> 2. the 'caron' description is inaccurate, actually ~c -> ç
>
> There is however no definition for creating 'a with breve' nor 'c with
> caron' in that input method
>
> 3. the dot above entry is also inaccurate, actually ~o -> õ /o -> ø .o -> .o
>
> There are definitions for /g -> ġ and .g -> ġ , however
IMO, these are bugs, not just documentation issues.
> Proposed solution:
>
> 1. I donʼt have one. Other input methods use ~a for either a with
> tilde or a with breve. We could just fix the docstring
>
> 2. We could do ~c -> č instead of ç , which is quite common in other
> input methods, and add ,c -> ç , which is in line
> with latin-postfix
>
> 3. This is a doc issue, we could replace that line with:
>
> dot above | / . | /g -> ġ .g -> ġ
>
> Thoughts?
I think we should make latin-prefix be consistent with latin-postfix.
Each one of the above is correct in the latter, AFAICT, so we should
just fix the problems in latin-prefix. E.g., ~a should produce both ã
and ă, ~c should produce č, and ġ should be produced by .g. I see no
reason to have these two behave inconsistently; do you?