From: zhangtao <zhangtao@zhangtao.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Matti Aarnio <matti.aarnio@zmailer.org>
Cc: LinuxKernel MailList <linux-kernel@vger.kernel.org>
Subject: Re: Which one should I contact about linux-kernel's NLS support such as codepage 936?
Date: Tue, 13 May 2003 09:35:06 +0800 [thread overview]
Message-ID: <20030513093506.03104c9e.zhangtao@zhangtao.org> (raw)
In-Reply-To: <1052737621.31246.7.camel@dhcp22.swansea.linux.org.uk>
On 12 May 2003 12:07:02 +0100
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Llu, 2003-05-12 at 03:05, zhangtao wrote:
> > Hi, Everyone,
> >
> > I have some patch about kernel's NLS, such as Codepage 936, 932, 949, 950.
> >
> > How can I contact the owner or public my patch ?
>
> I saw then and while they look ok I've been trying to find someone
> familiar with these code pages to review them
>
>
Linux Kernel 2.4.x NLS Patch, This Patch is used to correct problems of translation tables of CP932, CP936, CP949 and CP950.
There are 2 problems:
1. Translation Tables
In the "linux/fs/nls_cp936.c (ncl_cp932.c, nls_cp949.c and nls_cp950.c)", the translation tables were downloaded from
http://www.microsoft.com/typography/unicode/unicodecp.htm,
but the page was not found. The new Codepage is located at:
http://www.microsoft.com/globaldev/reference/cphome.mspx.
After examination the old one and new one, can find much more different,
e.g., 0x8179 in the CP936 should be corresponding with 0x4E82 in Unicode,
NOT 0xF91B. So, need rebuid the C program.
2. Area between 0x80 and 0xFF in the Unicode
The area between 0x80 and 0xFF in the Unicode, is not be corresponding with CP932, CP936, CP949 and CP950: part of this can have corresponding letters,
others not have. The old uni2char() function is not correct for dealing with this area, because it let 0x80-0xFF keep the same, but it's not true.
e.g., the Unicode letter 0x00A4 should be corresponding with 0xA1E8 of the Codepage 936, not keep itself.
next prev parent reply other threads:[~2003-05-13 1:22 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 [this message]
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
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=20030513093506.03104c9e.zhangtao@zhangtao.org \
--to=zhangtao@zhangtao.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.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).