From: Eli Zaretskii <eliz@gnu.org>
To: Kierin Bell <fernseed@fernseed.me>
Cc: 75448@debbugs.gnu.org
Subject: bug#75448: [PATCH] Fix documentation of Iroquoian input methods
Date: Thu, 09 Jan 2025 08:18:33 +0200 [thread overview]
Message-ID: <86ikqo33ye.fsf@gnu.org> (raw)
In-Reply-To: <87cygwom6n.fsf@fernseed.me> (message from Kierin Bell on Wed, 08 Jan 2025 19:39:12 -0500)
> From: Kierin Bell <fernseed@fernseed.me>
> Date: Wed, 08 Jan 2025 19:39:12 -0500
>
> This patch fixes a typo in the documentation for Iroquoian input methods
> for the Oneida endonym, propagated by copy-paste into comments,
> docstrings, and the NEWS entry. The previous spelling 'Onʌyota:ká:' was
> missing the third syllable and also used an idiosyncratic orthography.
> There are two common orthographic variants that I've seen:
> 'Onʌyote’a·ká·' (common in community language programs) and
> 'Onyotaˀa·ká·' (used in Karin Michelson's 2002
> 'Oneida-English/English-Oneida Dictionary'). I opted for the former.
Since these are very delicate matters, I'd like us to go by the
orthography that is really widely accepted. In Wikipedia
(https://en.wikipedia.org/wiki/Oneida_language), I see "onʌjotaʔaːka"
and "onʌjoteʔaːkaː", which is different from what you show. I wonder
what should we use, given so many different variants.
> There is also a small fix for an incorrect input key given in one of the
> input method docstrings.
I agree that factually the input method behaves as you describe in
your patch, but is it not more reasonable to change the code to behave
as the documentation says? Why should '-' after 'n' produce ñ? It
sounds like using '~' for that is better mnemonically?
Thanks.
next prev parent reply other threads:[~2025-01-09 6:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 0:39 bug#75448: [PATCH] Fix documentation of Iroquoian input methods Kierin Bell
2025-01-09 1:28 ` Stefan Kangas
2025-01-09 6:18 ` Eli Zaretskii [this message]
2025-01-09 7:11 ` Stefan Kangas
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=86ikqo33ye.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=75448@debbugs.gnu.org \
--cc=fernseed@fernseed.me \
/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).