Date: Tue, 17 Oct 1995 04:25:24 +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: "Kaleb S. KEITHLEY" <kaleb@x.org> Cc: hackers@freebsd.org Subject: Re: A couple problems in FreeBSD 2.1.0-950922-SNAP Message-ID: <Xl4OmWmeo3@ache.dialup.demos.ru> In-Reply-To: <199510170105.VAA25559@exalt.x.org>; from "Kaleb S. KEITHLEY" at Mon, 16 Oct 1995 21:05:24 EST References: <199510170105.VAA25559@exalt.x.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199510170105.VAA25559@exalt.x.org> Kaleb S. KEITHLEY
writes:
>> I know. And it is so when you don't have LANG or your char width > 8bits.
>> When you have LANG and your char width <= 8bits and you have
>> ENABLE_STARTUP_LOCALE variable set, lets call this case as
>> "ANSI extention". As you can see, this extention is well-controlled
>> by ENABLE_STARTUP_LOCALE.
>And this marvelous "extension" breaks programs, as you've found with
>the XFree86 xterm.
Well, shure, it seems that you not expect that propogating code
table to 8859-1 BREAKS XTERM in the same way! Because when LANG
set to 8859-1 our cases are equal!
>> Most of my agrument isn't premise but different behaviour of all
>> is*() macros for different charsets. What 8859-1 program treats
>> as isalpha isn't isalpha in other charset, for both input/output.
>> When program bound its input/output by is*() macros, it leads
>> into big trouble into your variant.
>I claim this is a non-issue. Terry claims it's expected behavior. Please
>provide an example or other proof that this is not the case.
Pretty simple, here some example of code:
do {
*s++ = getchar();
} while (!ispunct(*s));
When 8859-1 is set it stops on D7 and it will be right.
When 8859-5 is set is stops on D7 too, but D7 is letter.
>Because your way of fixing is in violation of ANSI/POSIX/ISO.
Well, it isn't only "my" way, I saw the same behavior in Xenix
internationalization f.e. :-) I agree now that it can't be default
case, so I withdraw my proposal to change ENABLE to DISABLE.
>When it's active it breaks correct programs. When it's inactive it isn't
It breaks no more than table propopgating, just right in the same way.
--
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?Xl4OmWmeo3>