From owner-freebsd-hackers Mon Mar 24 06:22:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA09698 for hackers-outgoing; Mon, 24 Mar 1997 06:22:00 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA09690 for ; Mon, 24 Mar 1997 06:21:52 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.5/8.8.5) with SMTP id JAA04889; Mon, 24 Mar 1997 09:21:17 -0500 (EST) Date: Mon, 24 Mar 1997 09:21:17 -0500 (EST) From: John Fieber To: junker@jazz.snu.ac.kr cc: freebsd-hackers@freebsd.org Subject: Re: EUC locales and XF86 3.2 for 2.2R? In-Reply-To: <199703240911.SAA27946@moderato.snu.ac.kr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 24 Mar 1997, Choi Jun Ho wrote: > 1. EUC locale support? ... > moderato:~% env LANG=C perl > ^D > moderato:~% env LANG=ko_KR.EUC perl > warning: setlocale(LC_CTYPE, "") failed. > warning: LC_ALL = "(null)", LC_CTYPE = "(null)", LANG = "ko_KR.EUC", > warning: falling back to the "C" locale. I'm just getting my feet wet in the FreeBSD l10n/i18n stuff, but I have discovered that to use an EUC or UTF locale, you must link with -lxpg4. Digging through the mailing list archives, I found a some messages the decision was made to remove >8-bit locale support from libc, but I didn't follow up and find the discussion of why. Could anyone involved in the decision provide a quick summary? On a related note, is anyone looking into implementing the Normative Addendum 1 to ANSI C? (multibyte/wide character support, see http://www.lysator.liu.se/c/na1.html for details) I made a (very) brief start but really don't have the time right now to work on it. -john