From: Kenichi Handa <handa@m17n.org>
To: Jihyun Cho <jihyun.jo@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] adjusting korean key bindings
Date: Mon, 15 Jun 2009 11:16:08 +0900 [thread overview]
Message-ID: <E1MG1k0-0002vj-H3@etlken> (raw)
In-Reply-To: <9d644d9b0906111954m6cb49cb6pe61716bbe060c980@mail.gmail.com> (message from Jihyun Cho on Fri, 12 Jun 2009 11:54:29 +0900)
In article <9d644d9b0906111954m6cb49cb6pe61716bbe060c980@mail.gmail.com>, Jihyun Cho <jihyun.jo@gmail.com> writes:
> F9 was used in a 101-key keyboard layout in the past.
> Currently, A 103-key keyboard layout or a 106-key keyboard layout is
> used in Korea.
> Both of them are added Hanja key and Hangul key.
> But some people are still using F9 and Shift-Space.
If what you mean is that some are still using F9 for
switching hangul<->hanja input methods, I think it's not the
time to change the key binding of F9. As your patch adds
Hangul_Hanja for converting the previous hangul to hanja,
there's no urgent need to change F9 too.
> A problem is a input method.
> Generally, The input method for conversion of Hanja is converting a
> completed Hangul letter to a Hanja letter.
> Most of Korean IMEs are implemented these method.
> The input method of emacs is little awkward.
Do you mean that we don't need the separate hanja input
method any more?
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2009-06-15 2:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 14:27 [PATCH] adjusting korean key bindings Jihyun Cho
2009-06-12 1:09 ` Kenichi Handa
2009-06-12 2:05 ` Jason Rumney
2009-06-12 2:54 ` Jihyun Cho
2009-06-15 2:16 ` Kenichi Handa [this message]
2009-06-15 12:21 ` Jihyun Cho
2009-06-16 6:43 ` Kenichi Handa
2009-06-17 8:06 ` Jihyun Cho
2009-06-17 11:44 ` Kenichi Handa
2009-06-17 15:34 ` Chong Yidong
2009-06-18 1:32 ` Kenichi Handa
2009-06-18 1:42 ` Kenichi Handa
2009-06-23 3:46 ` Kenichi Handa
2009-06-12 21:22 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1MG1k0-0002vj-H3@etlken \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=jihyun.jo@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.