From owner-freebsd-hackers Mon Oct 16 22:21:27 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA09864 for hackers-outgoing; Mon, 16 Oct 1995 22:21:27 -0700 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA09843 for ; Mon, 16 Oct 1995 22:21:21 -0700 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id GAA25338 for ; Tue, 17 Oct 1995 06:21:12 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id GAA26645 for freebsd-hackers@freebsd.org; Tue, 17 Oct 1995 06:21:11 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id XAA27289 for freebsd-hackers@freebsd.org; Mon, 16 Oct 1995 23:45:16 +0100 From: J Wunsch Message-Id: <199510162245.XAA27289@uriah.heep.sax.de> Subject: Re: A couple problems in FreeBSD 2.1.0-950922-SNAP To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Mon, 16 Oct 1995 23:45:15 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199510162034.NAA25305@phaeton.artisoft.com> from "Terry Lambert" at Oct 16, 95 01:34:10 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1667 Sender: owner-hackers@freebsd.org Precedence: bulk As Terry Lambert wrote: > > The problem with KOI-8 is that KOI-8 is a defacto standard, and is not > accepted by international standards bodies. Mostly because the most > popular BBS software in the area picked it up instead of 8859-9. The X Consortium finally agreed to accept koi8-r as a valid character set/encoding. :-) Well, if we would rely on things like ISO, we wouldn't use IP etc. and suffer from OSI/X.400 instead... > The problem is not in the blank areas of the locale. > > In point of fact, the ANSI standards for terminal control sequences > after ANSI 3.64 leave the codes in columns 0x80 and 0x90 to be used > to represent 8 bit command sequence introducers, which are the same > as an escape character followed by a character in columns 0x20 or 0x30. > Because of this, KOI-8 as a character set is not compatible with post > 3.64 ANSI terminal control sequence standardization. Do you know KOI8-R? It doesn't even touch those areas. This is NOT IBM's code page crime. KOI8-R does basically use the same printable characters like ISO-8859-*. The most notable difference to the ISO-8859-* fonts is that KOI has the upper/lower case reversed for some obscure reason. > Really, they should be using the 8859 character set instead of KOI-8, > but there is understood to be a large historical investment in the > non-standard KOI-8 representation (unfortunately). You're sounding like the OSI protagonists when they started the German educational network project (WiN) here. :-) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)