From owner-freebsd-current Mon Jun 11 22:50:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id E8B9837B403 for ; Mon, 11 Jun 2001 22:50:13 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id HAA14190; Tue, 12 Jun 2001 07:50:07 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.4/8.11.4) id f5C5Wva02805; Tue, 12 Jun 2001 07:32:57 +0200 (MET DST) (envelope-from j) Date: Tue, 12 Jun 2001 07:32:57 +0200 From: Joerg Wunsch To: "Andrey A. Chernov" Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADS UP: locale names reorganization Message-ID: <20010612073257.B2752@uriah.heep.sax.de> Reply-To: Joerg Wunsch References: <20010610163853.A1166@nagual.pp.ru> <200106101537.f5AFavo33433@mail.uic-in.net> <200106102136.f5ALawu94200@uriah.heep.sax.de> <20010611020547.A1379@nagual.pp.ru> <20010611082525.F94133@uriah.heep.sax.de> <20010611160108.A34164@nagual.pp.ru> <20010611212016.K94133@uriah.heep.sax.de> <20010611233423.A48057@nagual.pp.ru> <20010611235223.A48405@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010611235223.A48405@nagual.pp.ru>; from ache@nagual.pp.ru on Mon, Jun 11, 2001 at 11:52:23PM +0400 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG As Andrey A. Chernov wrote: > I.e. theoretically right now we can reduce locale names to two > components (language and territory) since we have in -current (but > not in -stable) nl_langinfo(CODESET), but not to one component > (language) since there is no standard function to get territory. I thought of two components, like ru_RU, en_US, or de_DE. AFAICT, that's the common practice i've seen in the other Unices. > But then we need to rewrite all old programs which parse LANG > directly to use nl_langinfo(CODESET). I didn't know that programs parse the name of the locale directly, i always thought they just use the contents of files pointed to by this name (under /usr/share/locale/), i. e. the actual local name would be opaque to the application. Do you have an example of a program parsing the name? I can't imagine right now who does it and why... Apart from that, those old applications would fall over the locale name change anyway (e. g. they expect "de_DE.ISO_8859-1" but find "de_DE.ISO8859-1" which they are not prepared to handle), so that's really a good reason to introduce the lang_TERRITORY shorthands by the same time (i'm speaking of -current only!). -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message