unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Jihyun Cho <jihyun.jo@gmail.com>
Cc: usenet@pusto.de, emacs-devel@gnu.org
Subject: Re: cp949 support
Date: Wed, 17 Jun 2009 20:20:10 +0900	[thread overview]
Message-ID: <E1MGtBa-0004vN-FG@etlken> (raw)
In-Reply-To: <9d644d9b0906170107o2e7f5d82j46882620b5a968b1@mail.gmail.com> (message from Jihyun Cho on Wed, 17 Jun 2009 17:07:36 +0900)

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

> In the past, someone has submitted a patch that is similar with this.
> (http://lists.gnu.org/archive/html/emacs-devel/2008-03/msg01700.html)

Oops, I have forgotten about that mail.

> They have different code-space between this patch and the old patch.
> Which is the correct code-space?

Af far as I see /usr/share/i18n/charmaps/CP949.gz, it seems
that the current one is correct.

> I applied this patch, but some Hangul letters in CP949 region are
> shown incorrectly.
> For example, the Hangul letter "HANGUL SYLLABLE HAEH" is shown "HANGUL
> SYLLABLE JWIG" in this patch.
> But the old patch works well.

How did you show those letters in Emacs?  By
list-charset-chars?  Please tell me the Unicode code point
of those two characters.

---
Kenichi Handa
handa@m17n.org




  reply	other threads:[~2009-06-17 11:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15 21:11 cp949 support Eduard Wiebe
2009-06-16  0:58 ` Kenichi Handa
2009-06-17  8:07   ` Jihyun Cho
2009-06-17 11:20     ` Kenichi Handa [this message]
2009-06-17 20:54       ` Eduard Wiebe
2009-06-18  2:19         ` Jihyun Cho
2009-06-18 11:14           ` Kenichi Handa
2009-06-18 13:05             ` Chong Yidong
2009-06-18 21:33               ` User Ew
2009-06-19  0:40             ` Kenichi Handa
2009-06-20  8:42               ` Eduard Wiebe
2009-06-22  1:37                 ` Kenichi Handa
2009-07-01 12:39                 ` Kenichi Handa

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=E1MGtBa-0004vN-FG@etlken \
    --to=handa@m17n.org \
    --cc=emacs-devel@gnu.org \
    --cc=jihyun.jo@gmail.com \
    --cc=usenet@pusto.de \
    /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).