From owner-freebsd-hackers Tue Oct 17 12:00:33 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA03751 for hackers-outgoing; Tue, 17 Oct 1995 12:00:33 -0700 Received: from expo.x.org (expo.x.org [198.112.45.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA03746 for ; Tue, 17 Oct 1995 12:00:31 -0700 Received: from exalt.x.org by expo.x.org id AA10076; Tue, 17 Oct 95 14:59:59 -0400 Received: from localhost by exalt.x.org id OAA19177; Tue, 17 Oct 1995 14:59:57 -0400 Message-Id: <199510171859.OAA19177@exalt.x.org> To: ache@astral.msk.su Cc: hackers@freefall.FreeBSD.org Subject: Re: A couple problems in FreeBSD 2.1.0-950922-SNAP In-Reply-To: Your message of Tue, 17 Oct 1995 20:29:46 EST. Organization: X Consortium Date: Tue, 17 Oct 1995 14:59:56 EST From: "Kaleb S. KEITHLEY" Sender: owner-hackers@FreeBSD.org Precedence: bulk > In message <199510171353.JAA08843@exalt.x.org> Kaleb S. KEITHLEY > writes: > > > >> In message <199510170809.SAA07948@rf900.physics.usyd.edu.au> David > >> Dawes writes: > >> > >> >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. > >> > >> Sigh. Why they not asking what preferences russsians have? > > >Because the X Consortium is a Standards Body. When there is an existing > >standard for something we prefer to follow it (Like RFC 821/822). In the > >face of a "real" standard, a de facto standard doesn't count. > > What do you mean by "real"? KOI8-R has two references now, they are > RFC 1489 (description) and RFC 1700 (registration as valid MIME > charset name). Is it enough for "real"? If you mean only ISO by "real", > why you refer RFC 822? > As far as SMTP is concerned I'm not aware that any of the standards bodies have a standard for that; therefore RFC 822 is the best thing available. When Terry refered to KOI8-R as a de facto standard you said nothing to indicate that that was an unfair or inaccurate characterization; therefore I presumed that Terry was correct in calling it a de facto standard. The fact that KOI8-R has been codified in an RFC notwithstanding, there is an ISO standard (irrespective of how useful most Russians think it is), and an ISO Standard carries a lot more weight than an RFC; therefore the X Consortium would still prefer to ship ISO8859-5 over KOI8-R in the Sample Implementation. Note that the X Consortium doesn't ship a lot of fonts for the various encodings that our members do support, e.g.: Hewlett Packard "roman8" and "HP-JAPANESEEUC" encoded fonts, "ibm-special" and "adobe- fontspecific" to name just a few. Those are left for vendors, VARs and other third parties like XFree86 to handle in their products. -- Kaleb KEITHLEY X Consortium