From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: latin-prefix input method niggles
Date: Thu, 10 Jan 2019 21:33:24 +0200 [thread overview]
Message-ID: <83y37sgvej.fsf@gnu.org> (raw)
In-Reply-To: <m2bm4o4ase.fsf@gmail.com> (message from Robert Pluim on Thu, 10 Jan 2019 19:39:29 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> 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?
next prev parent reply other threads:[~2019-01-10 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 18:39 latin-prefix input method niggles Robert Pluim
2019-01-10 19:33 ` Eli Zaretskii [this message]
2019-01-10 20:36 ` Robert Pluim
2019-01-11 7:05 ` Eli Zaretskii
2019-01-11 10:58 ` Robert Pluim
2019-01-11 19:12 ` Eli Zaretskii
2019-01-14 10:25 ` Robert Pluim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y37sgvej.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rpluim@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).