Date: 28 Nov 2000 20:54:40 +0900 From: CHOI Junho <cjh@kr.FreeBSD.ORG> To: itojun@iijlab.net Cc: "Michael C . Wu" <keichii@peorth.iteration.net>, freebsd-i18n@FreeBSD.ORG Subject: Re: NetBSD libintl, import of CITRUS * Message-ID: <86elzwtipr.fsf@gnomaniac.myhome> In-Reply-To: itojun@iijlab.net's message of "Tue, 28 Nov 2000 14:26:57 %2B0900" References: <14892.975389217@coconut.itojun.org>
index | next in thread | previous in thread | raw e-mail
>>>>> "i" == itojun <itojun@iijlab.net> writes:
> Regarding BSDL gettext, is it "finalized?"
i> not really. libintl (gettext) works just like GNU gettext, so it works
i> as GNU gettext replacement. however, our goal is much more complete
i> system - we don't want to hardcode our library to certain locale.
i> current gettext library (both GNU and CITRUS) assumes that you are
i> using single encoding for setlocale(3) and the message catalog file.
i> for example, if your $LANG equals to ko_KR.eucKR, message catalog file
i> must be encoded in euc-kr. we would like to make them more independent
In recent glibc(2.2), it converts its encoding according to LC_CTYPE
LC_CTYPE=ko_KR LC_MESSAGES=ja_JP foo
foo: <Japanese text converted into euc-kr>
Although it is not complete(euc-jp != euc-kr) but at least Kana and
some Kanji existing in euc-kr will be shown(maybe glibc does euc-jp ->
UCS4 -> euc-kr conversion).
I don't know internals of citrus code, but can we do this?
i> (like allowing ksc5601 catalog file).
ksx1001(ksc5601) is CCS... we may have euc-kr or utf-8 for Korean catalog.
--
+++ Any opinions in this posting are my own and not those of my employers +++
CHOI Junho [now sleeping] <http://www.kr.FreeBSD.org/~cjh>;
[when sleeping] <cjh@kr.FreeBSD.ORG> <cjh@FreeBSD.ORG> <cjh@wdb.co.kr>
Korea FreeBSD Users Group/www.kr.FreeBSD.org Web Data Bank/www.wdb.co.kr
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-i18n" in the body of the message
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86elzwtipr.fsf>