From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: zhangtao <zhangtao@zhangtao.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Matti Aarnio <matti.aarnio@zmailer.org>,
LinuxKernel MailList <linux-kernel@vger.kernel.org>
Subject: Re: About NLS Codepage 932
Date: Tue, 13 May 2003 21:23:18 +0900 [thread overview]
Message-ID: <87d6int4qx.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <20030513101740.626a06a5.zhangtao@zhangtao.org>
Just FYI,
zhangtao <zhangtao@zhangtao.org> writes:
> The big different is the area of Char To Unicode, the lead byte is :
> 0xF0, 0xF1, 0xF2, 0xF3, 0xF4, 0xF5, 0xF6, 0xF7, 0xF8, 0xF9
>
> In the Microsoft's table (http://www.microsoft.com/globaldev/reference/dbcs/932.htm), they are EMPTY!
These are UDC (User defined charactors).
> But in the Mit edu's CP932.TXT (http://web.mit.edu/afs/dev.mit.edu/source/src-current/third/libiconv/tests/CP932.TXT), they have corresponding letters.
Looks like using http://www.opengroup.or.jp/jvc/cde/ucs-conv-e.html.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2003-05-13 12:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 2:05 Which one should I contact about linux-kernel's NLS support such as codepage 936? zhangtao
2003-05-12 8:00 ` Matti Aarnio
2003-05-12 11:01 ` zhangtao
2003-05-12 11:07 ` Alan Cox
2003-05-13 1:35 ` zhangtao
2003-05-13 1:48 ` [PATCH] NLS Codepage 936 - Part 1 zhangtao
2003-05-13 1:50 ` [PATCH] NLS Codepage 936 - Part 2 zhangtao
2003-05-13 1:54 ` [PATCH] NLS Codepage 949 zhangtao
2003-05-13 1:58 ` [PATCH] NLS Codepage 950 - Part 1 zhangtao
2003-05-13 1:59 ` [PATCH] NLS Codepage 950 - Part 2 zhangtao
2003-05-13 2:17 ` About NLS Codepage 932 zhangtao
2003-05-13 12:23 ` OGAWA Hirofumi [this message]
2003-05-14 1:33 ` zhangtao
2003-05-14 13:08 ` OGAWA Hirofumi
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=87d6int4qx.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.org \
--cc=zhangtao@zhangtao.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.
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 NNTP newsgroup(s).