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: Tue, 16 Jun 2009 15:43:58 +0900 [thread overview]
Message-ID: <E1MGSOk-0007LB-E4@etlken> (raw)
In-Reply-To: <9d644d9b0906150521o23e54620v779832cc8df8e12@mail.gmail.com> (message from Jihyun Cho on Mon, 15 Jun 2009 21:21:44 +0900)
In article <9d644d9b0906150521o23e54620v779832cc8df8e12@mail.gmail.com>, Jihyun Cho <jihyun.jo@gmail.com> writes:
> > Do you mean that we don't need the separate hanja input
> > method any more?
> What do you mean the "separate hanja input method"?
> If it means the method included in Emacs, we need it.
I mean the file leim/quail/hanja.el.
> I agree that F9 should be maintained as conversion key of Hanja.
> But the method `quail-hangul-switch-hanja' is not a general way in Korea.
> Korean people don't switch the input mode to use Hanja.
> We just input a Hangul Letter, then F9 will convert the Letter to Hanja.
> I think it's more simple than the method 'quail-hangul-switch-hanja'
> for Korean user.
It seems that we are miscommunicating. I'm not discussing
whether "F9 should be maintained as conversion key of
Hanja." As your patch doesn't change the f9 binding in
hangul-im-keymap, I don't have to argue about it.
What I want to know is how important the change of f9
binding in korean-key-bindings is.
> - (global [f9] quail-hangul-switch-hanja nil)
> + (global [f9] hangul-to-hanja-conversion nil)
I asked you:
> The key-binding of F9 for quail-hangul-switch-hanja is what
> suggested long ago by a Korean person (I forgot who was
> that). Has the usage of F9 in Korea been changed in these
> days?
and you replied as this:
> But some people are still using F9 and Shift-Space.
But now you say:
> But the method `quail-hangul-switch-hanja' is not a general way in Korea.
> Korean people don't switch the input mode to use Hanja.
I'm now confused.
If no one use the facility of quail-hangul-switch-hanja
nowadays, there's no reason to keep the current f9 binding
in korean-key-bindings. But if some people still uses it,
we should not change it now.
So, which is the case?
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2009-06-16 6:43 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
2009-06-15 12:21 ` Jihyun Cho
2009-06-16 6:43 ` Kenichi Handa [this message]
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
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=E1MGSOk-0007LB-E4@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 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).