From owner-freebsd-hackers Wed Jun 10 22:54:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA27448 for freebsd-hackers-outgoing; Wed, 10 Jun 1998 22:54:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from waru.life.nthu.edu.tw (waru.life.nthu.edu.tw [140.114.98.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA27398 for ; Wed, 10 Jun 1998 22:54:24 -0700 (PDT) (envelope-from frankch@waru.life.nthu.edu.tw) Received: (from frankch@localhost) by waru.life.nthu.edu.tw (8.8.8/8.8.8) id NAA22927; Thu, 11 Jun 1998 13:56:44 +0800 (CST) (envelope-from frankch) Message-ID: <19980611135643.05642@waru.life.nthu.edu.tw> Date: Thu, 11 Jun 1998 13:56:43 +0800 From: Chen Hsiung Chan To: freebsd-hackers@FreeBSD.ORG Subject: i18n - what I can do for it? Mime-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.88 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found there're some interesing discussions about i18n on this list, so I subscribe to it. I have done some minor hack to libc(xpg4 part) to make it support big5, the encoding widely used in Taiwan and HongKong. The patches are located: http://waru.life.nthu.edu.tw/~frankch/locale/ These patches are toward some version between 2.2.5 and 2.2.6, so they might not applied cleanly to other systems. I am not sure about the way it is done. In fact big5 is not a good encoding (not conform to ISO-2022), but I can not get rid of it (it is the de facto standard in Taiwan now). -- Chen-Hsiung Chan [¸âÂíºµ](BIG5) Department of Life Science http://waru.life.nthu.edu.tw/~frankch/ National Tsing Hua University email: frankch@waru.life.nthu.edu.tw Taiwan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message