From: Eli Zaretskii <eliz@gnu.org>
To: Grant Shoshin Shangreaux <grant@churls.world>
Cc: emacs-devel@gnu.org
Subject: Re: adding Lakota keyboard layouts
Date: Tue, 18 May 2021 14:24:47 +0300 [thread overview]
Message-ID: <83sg2ks2rk.fsf@gnu.org> (raw)
In-Reply-To: <87bl98vng2.fsf@churls.world> (message from Grant Shoshin Shangreaux on Mon, 17 May 2021 20:29:49 -0500)
> From: Grant Shoshin Shangreaux <grant@churls.world>
> Date: Mon, 17 May 2021 20:29:49 -0500
>
> I've created some keyboard layouts for the Lakota language using
> quail-define-package and quail-define-rules. I'd like to commit them to
> Emacs itself, and would appreciate any suggestions or best practices for
> adding them. It looks like they might belong in the lisp/international/
> directory?
It should be in lisp/leim/quail/.
Lakota uses the Latin script, right? So I think your input method(s)
should be in the latin-*.el files, depending on whether they are
prefix or postfix. Does that sound right?
> If I understand the contribution guide correctly, I can send the patch
> to the bugs list. I have FSF assignment straightened out. Thanks in
> advance for any advice!
Thanks. As Robert said, please read CONTRIBUTE and format
accordingly. We generally prefer the patches to be formatted by
"git format-patch" relative to the current master branch, if that is
feasible for you.
next prev parent reply other threads:[~2021-05-18 11:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 1:29 adding Lakota keyboard layouts Grant Shoshin Shangreaux
2021-05-18 8:51 ` Robert Pluim
2021-05-18 11:24 ` Eli Zaretskii [this message]
2021-05-23 16:47 ` Grant Shoshin Shangreaux
2021-05-25 8:31 ` Robert Pluim
2021-06-18 15:31 ` Grant Shoshin Shangreaux
2021-06-20 11:06 ` Eli Zaretskii
2021-06-20 14:48 ` 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=83sg2ks2rk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=grant@churls.world \
/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).