Date: Wed, 11 Jan 1995 22:39:29 +0300 From: "Andrew A. Chernov, Black Mage" <ache@astral.msk.su> To: "Andrew V. Stesin" <stesin@elvisti.kiev.ua> Cc: freebsd-hackers@FreeBSD.org Subject: Re: Localization stuff? Message-ID: <vCnF35l0i2@astral.msk.su> In-Reply-To: <199501111633.SAA29660@office.elvisti.kiev.ua>; from "Andrew V. Stesin" at Wed, 11 Jan 1995 18:33:18 %2B0200 (EET) References: <199501111633.SAA29660@office.elvisti.kiev.ua>
index | next in thread | previous in thread | raw e-mail
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 <alex@elvisti.kiev.ua>)
>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
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?vCnF35l0i2>