From: Jihyun Cho <jihyun.jo@gmail.com>
To: Kenichi Handa <handa@m17n.org>
Cc: Eduard Wiebe <usenet@pusto.de>, emacs-devel@gnu.org
Subject: Re: cp949 support
Date: Wed, 17 Jun 2009 17:07:36 +0900 [thread overview]
Message-ID: <9d644d9b0906170107o2e7f5d82j46882620b5a968b1@mail.gmail.com> (raw)
In-Reply-To: <E1MGN0F-0006bM-ES@etlken>
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)
They have different code-space between this patch and the old patch.
Which is the correct code-space?
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.
2009/6/16 Kenichi Handa <handa@m17n.org>:
> In article <861vpldwy5.fsf@nirvana.pusto.de>, Eduard Wiebe <usenet@pusto.de> writes:
>
>> the following patch adds cp949 charset support to Emacs.
>> Btw, i compared etc/charsets/CP949-2BYTE.map with
>> http://unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WINDOWS/CP949.TXT and
>> found no descrepances.
>
>> 2009-06-15 Eduard Wiebe <usenet@pusto.de>
>
>> * international/mule-conf.el: Add cp949-2-byte, cp949.
>
> Thank you. I installed your change.
>
> ---
> Kenichi Handa
> handa@m17n.org
>
>
>
next prev parent reply other threads:[~2009-06-17 8:07 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 [this message]
2009-06-17 11:20 ` Kenichi Handa
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9d644d9b0906170107o2e7f5d82j46882620b5a968b1@mail.gmail.com \
--to=jihyun.jo@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
--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 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.