Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Oct 1995 02:40:38 +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:        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:  <yZsrkWmKU1@ache.dialup.demos.ru>
In-Reply-To: <199510162233.PAA25657@phaeton.artisoft.com>; from Terry Lambert at Mon, 16 Oct 1995 15:33:03 -0700 (MST)
References:  <199510162233.PAA25657@phaeton.artisoft.com>

next in thread | previous in thread | raw e-mail | index | archive | help
In message <199510162233.PAA25657@phaeton.artisoft.com> Terry Lambert
    writes:

>> 2) It breaks all >=8bit charsets which names != 8859-1.

>This is patently false.  What results is a predominantly 8-bit clean
>interface that has 0x00-0x1f,0x80-0x9f shown a controls, and everything
>else shown as printable characters.

>This is valid for all 8859-x display/input systems, since the reuse of
>the code points are not transformed by this (8859-x does not encode
>characters in those locations).

You consider one very simple case (isprint/iscontrol only) and think
that it is a proof. What you can say about ispunct() f.e.?
It is clearly differ into 8859-1 and 8859-5 f.e., islower/isupper differs
too. tolower/toupper differs too. Even isalpha differs.

>The only potentially incorrect behaviour is on blanks not being interpreted
>as blanks.  If you want a blank, you shouldn't be using some wild code
>point other than 0x20 anyway.  You get what you deserve.

Well, isspace differs too.

>The problems you will encounter in this circumstance are all *very*
>specific to cases where a single file system is being used by multiple
>nationalities of clients.

No it is different problem. By setting LANG for something != 8859-1
(for programs that understands it) I assume that programs which
not understands it still works right.
If they are strict ASCII, I automatically protected from any
unwanted effects. If they are 8859-1 I need to classify
various unwanted effects for each != 8859-1 charset as
'default undefined behaviour'.
-- 
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?yZsrkWmKU1>