Re: Questions about Chinese i18n (zh_TW.Big5 locale)
At 05:09 -0700 1999-03-10, Anthony Fok wrote:
I received an e-mail last week from Tung-Han Hsieh, the current main
author of the excellent xcin-2.3.04 package, the X Chinese INput
server. As he develops xcin-2.5, which will be compliant with C and
X11's locale standards, he is also actively involved in the Chinese
Linux Extension (CLE) Project as they strive towards I18N/L10N for the
Chinese community. They have incorporated the zh_TW.Big5 locale into
glibc-2.1, but are running into some problems.
Here is my rough translation of his e-mail message. (My English isn't
that good, so I hope I didn't make too many mistakes or misinterpret
Tung-Han's words. :-) His original message in Chinese is after the
translated one. :-) Thanks for your help! :-)
I will reply to the translated version point by point.
----- Forwarded message from Tung-Han Hsieh <email@example.com> >
Date: Tue, 2 Mar 1999 14:28:22 +0800
From: Tung-Han Hsieh <firstname.lastname@example.org>
Subject: Questions about i18n
X-Mailer: Mutt 0.91.2
Content-Type: text/plain; charset=iso-8859-1
Here is my question: Could I give you a copy of our locale-def to
Debian's glibc-2.1 maintainer(s) or the i18n group for testing? If you
find that it could be a bug in glibc-2.1, could Debian help fix the
bug, and then forward the bug report or patch to GNU? And when the
problem is corrected, could Debian accept our zh_TW.Big5 file as part
of the official release? To whom should I report these problems? Or
should I discuss with GNU (FSF) directly?
I think it would be best to deal with the glibc developers directly.
I don't know much about locales and thus it would be tough for me to
tell a glibc problem from a problem with the locale definition itself.
I am willing to add the locale to the Debian package once the
problem(s) are solved.
Actually, I don't feel too comfortable to contact GNU/FSF directly
since my copy of glibc-2.1 has been patched by Debian and may not be
the latest version, so I am not sure how to report the problem, and
would like to ask you [Debian developers] for help.
Version 2.1 is the latest release version, and the only patch in the
Debian package is a small fix for a potential security issue taken
from the glibc CVS tree.
I suggest using the `glibcbug' script to report the problem(s).
Joel Klecker (aka Espy) <URL:http://web.espy.org/>