all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Jihyun Cho <jihyun.jo@gmail.com>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [PATCH] adjusting korean key bindings
Date: Wed, 17 Jun 2009 20:44:13 +0900	[thread overview]
Message-ID: <E1MGtYr-0004xJ-8N@etlken> (raw)
In-Reply-To: <9d644d9b0906170106r1955c983jf7309e1a49158c01@mail.gmail.com> (message from Jihyun Cho on Wed, 17 Jun 2009 17:06:39 +0900)

In article <9d644d9b0906170106r1955c983jf7309e1a49158c01@mail.gmail.com>, Jihyun Cho <jihyun.jo@gmail.com> writes:

> We are miscommunicating.
> I understood that you were concerning about users who are still using F9.
> And what I want to tell you about is, those
> functions(`quail-hangul-switch-hanja', `hangul-to-hanja-conversion')
> are doing same job(to input Hanja), but using different ways.

Yes, I understand that.

> If you think the backward compatibility is a problem, please just
> apply the function 'hangul-to-hanja-conversion' in my patch for many
> users to want to customize a keymap.
> And I have one more asking. There is no bindings for
> 'Hangul','Hangul_Hanja'. Would you add these bindings?

Then, to summarize the requested changes:

o It doesn't change the previous usage.
o It adds new key-binding for 'Hangul' and 'Hangul_Hanja'
  keys.  They are almost the standard keys for Korean users.
o It modifies hangul-to-hanja-conversion so that it can be called
  even when korean input method is off.
o Currently the special key bindings for Korean is not
  documented.  So, the change does't require updating the
  manual.  But, of course, documenting them somewhere is
  preferable.

In article <jwvmy8ddubv.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:

> I don't understand enough of the subject to judge, really.  Does the
> change require updating the manual?  Does it change previous usage, or
> just add new one?

Please see above.

> We're really close to a release now, so I'd rather not make such changes
> so late in the game.

I understand that, but, for Korean users, I think this
change improves the usability very much.

---
Kenichi Handa
handa@m17n.org




  reply	other threads:[~2009-06-17 11:44 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
2009-06-17  8:06           ` Jihyun Cho
2009-06-17 11:44             ` Kenichi Handa [this message]
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=E1MGtYr-0004xJ-8N@etlken \
    --to=handa@m17n.org \
    --cc=emacs-devel@gnu.org \
    --cc=jihyun.jo@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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.