unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jihyun Cho <jihyun.jo@gmail.com>
To: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] adjusting korean key bindings
Date: Fri, 12 Jun 2009 11:54:29 +0900	[thread overview]
Message-ID: <9d644d9b0906111954m6cb49cb6pe61716bbe060c980@mail.gmail.com> (raw)
In-Reply-To: <E1MEvGv-0008NY-EX@etlken>

2009/6/12 Kenichi Handa <handa@m17n.org>:
> In article <9d644d9b0906110727r7fc75080gf8f10ea47623db7f@mail.gmail.com>, Jihyun Cho <jihyun.jo@gmail.com> writes:
>
>> I adjusted a keymap.
>> Many korean people are using a `Hanja' key to convert Hangul to Hanja
>> and a `Hangul' key to toggle input method.
>> As a keymap was adjusted, I modified a `hangul-to-hanja-conversion' function.
>
> Thank you.  Although the patch need subtle modifications, it
> seems that it surely improves usability for Korean users.
> But, this change breaks backward compatibility.
>
> -    (global [f9]  quail-hangul-switch-hanja nil)
> +    (global [f9] hangul-to-hanja-conversion nil)
>
> 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?

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.

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.

> By the way, Yidong and Stefan, the change don't fit in the
> criteria of what can be intalled now, but, for Korean users,
> I think it's worth taking your time to consider whether or
> not to install it.  Please decide it.  I believe the change
> is quite safe.
>
> ---
> Kenichi Handa
> handa@m17n.org
>




  parent reply	other threads:[~2009-06-12  2:54 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 [this message]
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
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=9d644d9b0906111954m6cb49cb6pe61716bbe060c980@mail.gmail.com \
    --to=jihyun.jo@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.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).