From owner-freebsd-hackers Mon Oct 16 09:33:51 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA13616 for hackers-outgoing; Mon, 16 Oct 1995 09:33:51 -0700 Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id JAA13608 for ; Mon, 16 Oct 1995 09:33:35 -0700 Received: by sequent.kiae.su id AA00618 (5.65.kiae-2 ); Mon, 16 Oct 1995 20:17:31 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Mon, 16 Oct 95 20:17:28 +0300 Received: (from ache@localhost) by ache.dialup.demos.ru (8.6.11/8.6.9) id TAA07948; Mon, 16 Oct 1995 19:16:21 +0300 To: "Kaleb S. KEITHLEY" Cc: hackers@freefall.FreeBSD.org References: <199510161555.LAA07471@exalt.x.org> In-Reply-To: <199510161555.LAA07471@exalt.x.org>; from "Kaleb S. KEITHLEY" at Mon, 16 Oct 1995 11:55:24 EST Message-Id: Organization: Olahm Ha-Yetzirah Date: Mon, 16 Oct 1995 19:16:21 +0300 (MSK) X-Mailer: Mail/@ [v2.40 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Re: A couple problems in FreeBSD 2.1.0-950922-SNAP Lines: 50 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 2017 Sender: owner-hackers@FreeBSD.org Precedence: bulk In message <199510161555.LAA07471@exalt.x.org> Kaleb S. KEITHLEY writes: >ASCII meets this criteria. ISO8859-1 also meets this criteria. There is >not requirement that you use the most minimally compliant character set. >I do not understand your insistence that the C locale be strictly ASCII >and no more. Well, do you see what POSIX work group means by "C" locale (attached at the end of the message?) >I claim that it would be useful in the C locale if the default char- >type table were to be nominally populated for 8859-1, i.e. excluding >the upper and lower designations. Just wondering, why you even need such damaged table... Some principles? :-) >You claim that doing so will break Russian and Japanese users. I claim >that these users won't be using the C locale anyway. The fact that your >locale support is broken and the utility programs are broken is merely >an argument that they should be fixed. :-) Sigh.... They == Russian/Japanese/Any users with charset != 8859-1, f.e. users with 8859-3. 1) They use _C_ locale for all not-setlocale-aware programs per POSIX: default behaviout is setlocale(LC_ALL, "C") at startup. 2) And they use _NATIVE_ locale for all setlocale-aware programs which calls setlocale(LC_ALL, "") f.e. in main(). Your propogating idea breaks case 1) (POSIX), i.e. breaks all not-setlocale-aware programs because 8859-1 rules mixed up with locale charset. I.e. 8859 treats native chars like they was 8859-1 chars. I cause that I see my native chars on the screen in strange places and I can even enter some of my native chars wich can cause unknown effects. Please, look more carefully on what I try to say (I try to say it in different ways already several times). -- 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