From owner-freebsd-hackers  Tue Oct 17 01:13:50 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id BAA13610
          for hackers-outgoing; Tue, 17 Oct 1995 01:13:50 -0700
Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA13586
          for <freebsd-hackers@freebsd.org>; Tue, 17 Oct 1995 01:13:24 -0700
Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.6.11/8.6.9) id SAA07948; Tue, 17 Oct 1995 18:09:27 +1000
From: David Dawes <dawes@rf900.physics.usyd.edu.au>
Message-Id: <199510170809.SAA07948@rf900.physics.usyd.edu.au>
Subject: Re: A couple problems in FreeBSD 2.1.0-950922-SNAP
To: joerg_wunsch@uriah.heep.sax.de
Date: Tue, 17 Oct 1995 18:09:27 +1000 (EST)
Cc: freebsd-hackers@freebsd.org
In-Reply-To: <199510162245.XAA27289@uriah.heep.sax.de> from "J Wunsch" at Oct 16, 95 11:45:15 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 894       
Sender: owner-hackers@freebsd.org
Precedence: bulk

>> 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.
>
>:-)

What the X Consortium did was to accept The XFree86 Project's request
to register the charset/encoding KOI8-R.  I don't think it implies
any more than that.  There are a lot of unusual or vendor-specific
chareset/encodings registered with them -- take a look in the xc/registry
file.

If they ship Cyrillic fonts with their next release, they've indicated
(to me at least) that their preference is to use the ISO8859-5 encoding.

What XFree86 would like to do in the next release, if possible, is allow
the Cyrillic fonts to be built with either KOI8-R or ISO8859-5 encodings.

David