From owner-freebsd-hackers Thu Jun 11 00:50:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14332 for freebsd-hackers-outgoing; Thu, 11 Jun 1998 00:50:19 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from coconut.itojun.org (root@coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14272 for ; Thu, 11 Jun 1998 00:50:11 -0700 (PDT) (envelope-from itojun@itojun.org) Received: from localhost (itojun@localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.8.8+3.0Wbeta12/3.6W) with ESMTP id QAA11479; Thu, 11 Jun 1998 16:48:42 +0900 (JST) To: CHOI Junho cc: Gary Kline , tlambert@primenet.com (Terry Lambert), hackers@FreeBSD.ORG In-reply-to: junker's message of 11 Jun 1998 15:43:06 JST. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: internationalization From: Jun-ichiro itojun Itoh Date: Thu, 11 Jun 1998 16:48:41 +0900 Message-ID: <11475.897551321@coconut.itojun.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Yes, iso-2022 families are quite important for supporting >> asian languages. Unicode is, for us Japanese, quite incomplete and >> unexpandable. >I don't understand why unicode is worse for Japanese. Just lack of >some Kanji glyphs? (someone in Japan pointed me a book but I couldn't >get the book...) For multilingualization Unicode is useless (as I wrote in the previous email to hackers). We already got a framework that is capable for multilingualization (iso-2022), we are already using it. euc-kr is one of iso-2022 family too, as you know. >> Yes, for Japanese, Chinese and Korean iso-2022 based model (euc-xx >> falls into the category) is really important. However, I personally >> believe that filenames must be kept in C locale for simplicity... >Yes, I agree. >For internationalization, I suggest GNU gettext support. Although glibc >or fileutils(except gnuls) is not used officially in the FreeBSD, >there are many other program supporting GNU gettext. For multiple >language messages, GNU gettext is used widely, so I think it is better >to port it into FreeBSD(as a port). I am Korean language >sub-maintainer in GNU NLS Project, but ironically I can't see the >messages translated by me in my FreeBSD machine... gnuls, bison, a2ps, >windowmaker, freetype need GNU gettext, but it is ignored in the phase >of port compilation... yes, I agree that NLS is another important portion for internationalizing applications. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message