From owner-freebsd-hackers Wed Jan 11 11:46:06 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA09315 for hackers-outgoing; Wed, 11 Jan 1995 11:46:06 -0800 Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id LAA09309 for ; Wed, 11 Jan 1995 11:46:03 -0800 Received: by sequent.kiae.su id AA00586 (5.65.kiae-2 for freebsd-hackers@freebsd.org); Wed, 11 Jan 1995 22:44:47 +0300 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id WAA00883; Wed, 11 Jan 1995 22:39:30 +0300 To: "Andrew V. Stesin" Cc: freebsd-hackers@FreeBSD.org References: <199501111633.SAA29660@office.elvisti.kiev.ua> In-Reply-To: <199501111633.SAA29660@office.elvisti.kiev.ua>; from "Andrew V. Stesin" at Wed, 11 Jan 1995 18:33:18 +0200 (EET) Message-Id: Organization: Olahm Ha-Yetzirah Date: Wed, 11 Jan 1995 22:39:29 +0300 X-Mailer: Mail/@ [v2.31 FreeBSD] From: "Andrew A. Chernov, Black Mage" X-Class: Fast Subject: Re: Localization stuff? Lines: 60 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 2480 Sender: hackers-owner@FreeBSD.org Precedence: bulk In message <199501111633.SAA29660@office.elvisti.kiev.ua> Andrew V. Stesin writes: >after seeing your message about FreeBSD localization issues, >we here (me and my collegue Alex Tatmanjants ) >decided to make an attempt of adding at least LC_COLLATE localization >part to the current code. It will be nice to implement whole family too at least for 8bit subset. >We are planning: >1. Obtaining the localization stuff from the latest FreeBSD-2 snapshot; >2. Making it to work under our 1.1.5 systems (hove it will do > out of the box); >3. Adding the LC_COLLATE functionality to the code; >4. Submitting the results to the main source tree. Better send results to me first for review, than I'll commit them to source tree. >We need the guidelines of someone from FreeBSD team for >doing this. The questions are: > What kind of functionality should be implemented > with respect to *BSD traditions and spirit? > I mean exactly the following: > -- should it be the reimplementation of SunOS-4 locale? > -- or straightforvard port of Linux stuff (c) Saukh? > -- or maybe BSDi folks are going to provide an implementation > in their new release and though it will be wise to > stay compatible with them? > -- or what will you suggest? Current LC_CTYPE locale is slightly rewritten (optimized for space, better ctype handling for signed 8bit chars) BSD 4.4Lite locale and based on Runes UTF coding. I am not shure, but seems that Linux and SunOS locales not support Runes, so it maybe good idea to write LC_COLLATE for 8bit subset only as first step, if it will be hard to make it for Runes encoding. In any case whole current scheme should be preserved. I think original BSD locale author not bothering to implement whole locale family, but maybe I am wrong. As external and user interface we should follow POSIX locale description, if it isn't conflict with current scheme. >We need a short pointer to the tools which are (or must be?) >used for playing with locale descriptions (what are they? there >aren't any in 1.1.5). Check mklocale code, there is locale data files too (currently koi8-r, iso8859-1 and Japan) -- Andrew A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849