bug#74170: [PATCH] Add input methods for Northern Iroquoian languages

[Eli Zaretskii <eliz@gnu.org>]

> From: Kierin Bell <fernseed@fernseed.me>
> Cc: 74170@debbugs.gnu.org
> Date: Sat, 02 Nov 2024 23:45:34 -0400
> 
> --- a/etc/NEWS
> +++ b/etc/NEWS
> @@ -815,6 +815,17 @@ DirectWrite rendering parameters.
>  To show color Emoji in Emacs, customize the default fontset to use a
>  color Emoji font installed on your system for the 'emoji' script.
>  
> +---
> +** New input methods for Northern Iroquoian languages.
> +Input methods are now implemented for all Five Nations Iroquois
> +languages in the Northern Iroquoian language family: 'mohawk-postfix'
> +(Mohawk [Kanien’kéha / Onkwehonwe’néha]), 'oneida-postfix' (Oneida
> +[Onʌyota:ká: / Ukwehuwehnéha]), 'cayuga-postfix' (Cayuga
> +[Gayogo̱ho:nǫhnéha:ˀ]), 'onondaga-postfix (Onondaga [[Onųdaʔgegáʔ]), and
> +`seneca-postfix' [Onödowá’ga:’]).  Additionally, there is a
> +general-purpose 'iroquoian-postfix' input method to facilitate writing
> +in the orthographies of the five languages simultaneously.

This is the wrong place for this NEWS entry.  Please put this entry
under Internationalization (where you will see another entry about a
new input method), and please made it a sub-entry of
Internationalization, i.e. start with "***", not "**".

> +(defconst iroquoian-mohawk-consonant-alist
> +  '((";;" ?\N{RIGHT SINGLE QUOTATION MARK})
> +    ("h" ?h)
> +    ("H" ?H)
> +    ("k" ?k)
> +    ("K" ?K)
> +    ("m" ?m)
> +    ("M" ?M)
> +    ("n" ?n)
> +    ("N" ?N)
> +    ("r" ?r)
> +    ("R" ?R)
> +    ("s" ?s)
> +    ("S" ?S)
> +    ("t" ?t)
> +    ("T" ?T)
> +    ("w" ?w)
> +    ("W" ?W)
> +    ("Y" ?Y)
> +    ("y" ?y)
> +    ;; Rare (ideophones and loan words):
> +    ("b" ?b)
> +    ("B" ?B)
> +    ("m" ?m)
> +    ("M" ?M)))

Can we please have doc strings for these defconst's, which explain the
role of each element of alist's associations?  For example, by looking
at the rest of the code, it sounds like most of the above will define
trivial rules that map, say, H into itself?  If so, do we really need
such rules in the input method?  Quail generally does that
automatically, i.e. a letter that has no mapping produces itself.  But
maybe I misunderstood the code and the role of the data of these
alists, which is why I think doc strings would be a good idea.

Thanks.