From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jihyun Cho Newsgroups: gmane.emacs.devel Subject: Re: cp949 support Date: Thu, 18 Jun 2009 11:19:05 +0900 Message-ID: <9d644d9b0906171919x3b05cc2eu6af3db8d113ee6cd@mail.gmail.com> References: <861vpldwy5.fsf@nirvana.pusto.de> <9d644d9b0906170107o2e7f5d82j46882620b5a968b1@mail.gmail.com> <868wjq1szl.fsf@nirvana.pusto.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1245291555 3012 80.91.229.12 (18 Jun 2009 02:19:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 18 Jun 2009 02:19:15 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eduard Wiebe Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 18 04:19:13 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MH7Dc-0001js-Jx for ged-emacs-devel@m.gmane.org; Thu, 18 Jun 2009 04:19:12 +0200 Original-Received: from localhost ([127.0.0.1]:40443 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MH7Db-0001AZ-R8 for ged-emacs-devel@m.gmane.org; Wed, 17 Jun 2009 22:19:11 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MH7DX-0001AK-S3 for emacs-devel@gnu.org; Wed, 17 Jun 2009 22:19:07 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MH7DW-0001A8-H0 for emacs-devel@gnu.org; Wed, 17 Jun 2009 22:19:06 -0400 Original-Received: from [199.232.76.173] (port=53054 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MH7DW-0001A5-Bk for emacs-devel@gnu.org; Wed, 17 Jun 2009 22:19:06 -0400 Original-Received: from yw-out-1718.google.com ([74.125.46.158]:12669) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MH7DW-0002Nj-1y for emacs-devel@gnu.org; Wed, 17 Jun 2009 22:19:06 -0400 Original-Received: by yw-out-1718.google.com with SMTP id 5so346827ywm.66 for ; Wed, 17 Jun 2009 19:19:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=6tc6aL1RsyO8AF2GXNF93KxR2ZgtkE5xveV21yA8ZF0=; b=XkJ+Zx7VMqHEHDWSNZ6mTwcYs+/jKEJyVAC4qVhmOUj+ORarNYp/6gFkgjYzc/KWwn FfpM4RPLP0sAH45O78MF5X12NhWzSYgP6ZJlDCxNNHXzioE6zCHe88xxD9mIl8yJVq+k pxa2Za2VUdxSsZNd+KEClzo+wn3JTvNwzjGew= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=jmU7TFXafSSyAYjfcHbPfb3VzL039+ar9AHM/b+kmJhe+rXUtZI6N6rcYqTEubGOUl 9+1PD3Yb6RzL6em/kMI50qQ5qzZqu1Bnk1/wJMbx02hg8+p8h6nfxz7ZMTUlj6n0wBTK eTCGjfHfl2zAIubUj0Bce2m6kzgUWw1Dzzrjg= Original-Received: by 10.151.143.8 with SMTP id v8mr2438594ybn.267.1245291545539; Wed, 17 Jun 2009 19:19:05 -0700 (PDT) In-Reply-To: <868wjq1szl.fsf@nirvana.pusto.de> X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:111571 Archived-At: 2009/6/18 Eduard Wiebe : > Kenichi Handa writes: > >> In article <9d644d9b0906170107o2e7f5d82j46882620b5a968b1@mail.gmail.com>= , Jihyun Cho 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. > > Hmm..!? > >> How did you show those letters in Emacs? =A0By >> list-charset-chars? > > The output of M-x list-charset-chars looks pretty good to me and accords > with http://msdn.microsoft.com/de-de/goglobal/cc305154(en-us).aspx > >> Please tell me the Unicode code point of those two characters. > > @Jihyun, have you following chars in mind? > > HANGUL SYLLABLE HAEH: =A0Unicode 0xd58f, CP949 0xc164 > HANGUL SYLLABLE JWIG: =A0Unicode 0xc951, CP949 0xc1e4 Yes. It looks very good to me, too. I ran the following test. First, I applied a old patch. I saved a file with VIM with the option "set fenc=3Dcp949". Then I loaded the file with EMACS. It is broken in my UTF-8 environment. So I was typing "M-x revert-buffer-with-coding-system", "cp949", then it looks well. After applying this patch, I ran a same test. It shows a wrong letter. I guess the problem is related to coding system. The problem that "HANGUL SYLLABLE HAEH" is shown "HANGUL SYLLABLE JWIG" occured in EUC-KR coding system. Because "HANGUL SYLLABLE HAEH" is not contained in EUC-KR region. But CP949 contains "HANGUL SYLLABLE HAEH". This patch could not fix it.