Date: Tue, 28 Nov 2000 21:01:51 +0900 From: itojun@iijlab.net To: CHOI Junho <cjh@kr.FreeBSD.ORG> Cc: "Michael C . Wu" <keichii@peorth.iteration.net>, freebsd-i18n@FreeBSD.ORG Subject: Re: NetBSD libintl, import of CITRUS * Message-ID: <19813.975412911@coconut.itojun.org> In-Reply-To: cjh's message of 28 Nov 2000 20:54:40 JST. <86elzwtipr.fsf@gnomaniac.myhome>
next in thread | previous in thread | raw e-mail | index | archive | help
>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). in the above case i believe we should bail, but anyway, it's good to know. >I don't know internals of citrus code, but can we do this? yes, the above behavior is needed for citrus gettext(3). we know the place where we need to call iconv(3) from within gettext(3), we have a /* XXX */ there. > i> (like allowing ksc5601 catalog file). >ksx1001(ksc5601) is CCS... we may have euc-kr or utf-8 for Korean catalog. oops, iso-2022-kr (RFC1557). itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-i18n" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19813.975412911>