From owner-freebsd-hackers Mon Oct 16 17:46:25 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA01363 for hackers-outgoing; Mon, 16 Oct 1995 17:46:25 -0700 Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id RAA01356 for ; Mon, 16 Oct 1995 17:46:20 -0700 Received: by sovcom.kiae.su id AA27979 (5.65.kiae-1 ); Tue, 17 Oct 1995 02:41:32 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Tue, 17 Oct 95 02:41:32 +0300 Received: (from ache@localhost) by ache.dialup.demos.ru (8.6.11/8.6.9) id CAA00513; Tue, 17 Oct 1995 02:40:39 +0300 To: Terry Lambert Cc: hackers@freefall.freebsd.org, kaleb@x.org References: <199510162233.PAA25657@phaeton.artisoft.com> In-Reply-To: <199510162233.PAA25657@phaeton.artisoft.com>; from Terry Lambert at Mon, 16 Oct 1995 15:33:03 -0700 (MST) Message-Id: Organization: Olahm Ha-Yetzirah Date: Tue, 17 Oct 1995 02:40:38 +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: 40 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 1829 Sender: owner-hackers@FreeBSD.org Precedence: bulk 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