From: Garid Zorigoo <garidzorigoo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 56617@debbugs.gnu.org
Subject: bug#56617: [PATCH] for Mongolian input
Date: Wed, 5 Apr 2023 16:47:17 +0900 [thread overview]
Message-ID: <CAEDgBW6Z0Zg=TJPreay-R+Yn6ZUhTp5knM1y1DdfoGSxLeDfiw@mail.gmail.com> (raw)
In-Reply-To: <83355eubnp.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2197 bytes --]
Thank you for you reply
> In other words, where did you take the idea of which letter to place on
which key?
Sorry, if the description was unclear.
I didn't invent this layout. Basically, this is the layout people get
when they change input-language on OS level (e.g. Windows and Linux).
I'm not sure where or when this was selected to be the Mongolian Keyboard
Layout.
At the moment, I can only find out following resources:
- https://en.wikipedia.org/wiki/Mongolian_Cyrillic_alphabet#Keyboard_layout
- https://learn.microsoft.com/en-us/globalization/keyboards/kbdmon.html
- http://kbdlayout.info/KBDMON/
> I'm asking because with the exception of 2 characters
This layout is still used like 99% of the Mongolian Computers (I think).
When I was a kid, I had to learn this layout in order to type.
And now, using other cyrillic input such as cyrillic-translit just
un-natural to me
(probably un-natural to others too).
> (and you just copied it in Emacs LEIM format)
From the technical side, I did copy the e-lisp code from various places.
To be honest, I still don't know what the code does or
what the code-structure is supposed to be .
Garid
On Wed, Apr 5, 2023 at 2:42 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Garid Zorigoo <garidzorigoo@gmail.com>
> > Date: Tue, 4 Apr 2023 17:39:51 +0900
> >
> > This is [patch] for Mongolian Input.
> >
> > I only added Mongolian layout into the `lisp/leim/quail/cyrillic.el` and
> sent it as a patch.
> >
> > Please note that my knowledge in elisp is basically zero.
> > So, If you have any improvement/modification, please go ahead.
>
> Thank you for your contribution.
>
> Is this keyboard layout already in use in some keyboards used for
> typing Mongolian (and you just copied it in Emacs LEIM format), or did
> you invent the layout yourself? In other words, where did you take
> the idea of which letter to place on which key? I'm asking because
> with the exception of 2 characters, the letters are all present in
> other Cyrillic input methods, but the arrangement of the keys is
> different, so I'd like to understand the reasons for the differences.
>
>
[-- Attachment #2: Type: text/html, Size: 3427 bytes --]
next prev parent reply other threads:[~2023-04-05 7:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 10:20 bug#56617: 28.1; No Mongolian option in input-method Garid Zorigoo
2022-07-17 15:54 ` Eli Zaretskii
2023-04-04 8:39 ` bug#56617: [PATCH] for Mongolian input Garid Zorigoo
2023-04-05 5:43 ` Eli Zaretskii
2023-04-05 7:47 ` Garid Zorigoo [this message]
2023-04-08 7:53 ` Eli Zaretskii
2023-04-08 10:51 ` Garid Zorigoo
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='CAEDgBW6Z0Zg=TJPreay-R+Yn6ZUhTp5knM1y1DdfoGSxLeDfiw@mail.gmail.com' \
--to=garidzorigoo@gmail.com \
--cc=56617@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).