Date: Tue, 17 Jan 1995 00:10:13 +0300 (MSK) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) <ache@astral.msk.su> To: joerg_wunsch@uriah.heep.sax.de, Terry Lambert <terry@lambert.org> Cc: hackers@freefall.freebsd.org, kaleb@x.org Subject: Re: A couple problems in FreeBSD 2.1.0-950922-SNAP Message-ID: <sZr2k6lWb2@ache.dialup.demos.ru> In-Reply-To: <199510162034.NAA25305@phaeton.artisoft.com>; from Terry Lambert at Mon, 16 Oct 1995 13:34:10 -0700 (MST) References: <199510162034.NAA25305@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199510162034.NAA25305@phaeton.artisoft.com> Terry Lambert
writes:
>> As Kaleb S. KEITHLEY wrote:
>> >
>> > As near as I can tell the SVR4 ls doesn't change its locale, yet still
>> > manages to do the right thing, probably because for most SVR4-en the C
>> > locale is full ISO8859-1. This leads me to believe that FreeBSD's ls
>> > probably doesn't need to change its locale either if the default chartype
>> > table is fully populated.
>>
>> So SVR4 would still break on koi8-r, for example. Either make it
>> right, or let it be.
>But not on 8859-x. For Coptic alphabets, that's 8859-9.
SVR4/Kaleb solution breaks any charset which != 8859-1.
>The problem with KOI-8 is that KOI-8 is a defacto standard, and is not
>accepted by international standards bodies. Mostly because the most
It accepted by IANA, see RFC 1700.
>popular BBS software in the area picked it up instead of 8859-9.
BSD software in the area uses CP866.
>The problem is not in the blank areas of the locale.
Why you even decide that problem is in the blank area?
>In point of fact, the ANSI standards for terminal control sequences
>after ANSI 3.64 leave the codes in columns 0x80 and 0x90 to be used
>to represent 8 bit command sequence introducers, which are the same
>as an escape character followed by a character in columns 0x20 or 0x30.
>Because of this, KOI-8 as a character set is not compatible with post
>3.64 ANSI terminal control sequence standardization.
When KOI8-R code table was designed, it was keeped in mind, so
0x80 range cotains less used chars which can be safely ommited.
>It is not unreasonable, then, for the code to function correctly in
>the 8-bit case for ISO 8859-x but not function correctly without an
>environment or (more preferrably) code change in the application for
>KOI-8.
Even 8859-2 becomes broken when C locale becomes 8859-1.
Read full discussion before answering.
>Really, they should be using the 8859 character set instead of KOI-8,
>but there is understood to be a large historical investment in the
>non-standard KOI-8 representation (unfortunately).
8859-5 us deadborn. Nobody use it currently. It was designed by
foreigners for russians, such attempts are always deadborn.
--
Andrey 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?sZr2k6lWb2>