From owner-freebsd-hackers Mon Oct 16 20:13:14 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA06546 for hackers-outgoing; Mon, 16 Oct 1995 20:13:14 -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 UAA06535 for ; Mon, 16 Oct 1995 20:13:09 -0700 Received: by sovcom.kiae.su id AA13471 (5.65.kiae-1 ); Tue, 17 Oct 1995 06:11:44 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Tue, 17 Oct 95 06:11:44 +0300 Received: (from ache@localhost) by ache.dialup.demos.ru (8.6.11/8.6.9) id GAA01285; Tue, 17 Oct 1995 06:05:01 +0300 To: Terry Lambert Cc: hackers@freefall.freebsd.org, joerg_wunsch@uriah.heep.sax.de, kaleb@x.org References: <199510170239.TAA26264@phaeton.artisoft.com> In-Reply-To: <199510170239.TAA26264@phaeton.artisoft.com>; from Terry Lambert at Mon, 16 Oct 1995 19:39:54 -0700 (MST) Message-Id: Organization: Olahm Ha-Yetzirah Date: Tue, 17 Oct 1995 06:05:01 +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: 39 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 1817 Sender: owner-hackers@FreeBSD.org Precedence: bulk In message <199510170239.TAA26264@phaeton.artisoft.com> Terry Lambert writes: >> >I can *potentially* see ispunct() (though I can't think of any >BS. Read XPG/3, which doesn't know about multibyte characters, yet >defines setlocale(). >It's true that calling an XPG/4 setlocale() in an 8-bit clean, multibyte >unaware program in a runic encoded/multibyte locale will fail. The >soloution is to fix the program. Right now we can't use setlocale() in any code because have XPG/4 in libc. Fixing any program for XPG/4 is very non-trivial task and you says that it not used in any case. All ports software which calls setlocale() assumes XPG/3, so it is already broken for runes. It seems that we needs to change 4 -> 3 and remove bloat taken by runic encoding. >> >KOI8 is a peculiar locale in that it doesn't follow the 8859-x rules >> >like it should. Like EBCDIC, it needs to die in the long term. On >> >> And WHY IT SHOULD DO anything? It is EXISTEN CODE TABLE and LOCALES >> must be adopted for it and not vice versa. I promise you that >> it never dies in nearest 20-40 years, its population grows >> whith each new Internet user. >That's too bad. I guess you will have to properly localize in order >to use software, then, instead of taking advantage of 8859-x formulation >rules to get 90% soloutions. Like you'd be able to do if the standard >you chose to use met those guidelines. I can't see why KOI8-R charset needs to follow 8859-x rules when setlocale() called, it simple becomes loaded as is. -- 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