Re: Character set issues again
John C Klensin <KLENSIN@infoods.unu.edu> Sat, 16 October 1993 01:37 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa17397; 15 Oct 93 21:37 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa17391; 15 Oct 93 21:37 EDT
Received: from ucdavis.ucdavis.edu by CNRI.Reston.VA.US id aa08313; 15 Oct 93 21:37 EDT
Received: by ucdavis.ucdavis.edu (4.1/UCD2.05) id AA08160; Fri, 15 Oct 93 17:56:52 PDT
X-Orig-Sender: ietf-wnils-request@ucdavis.edu
Received: from INFOODS.MIT.EDU by ucdavis.ucdavis.edu (4.1/UCD2.05) id AA19793; Fri, 15 Oct 93 13:21:28 PDT
Received: from INFOODS.UNU.EDU by INFOODS.UNU.EDU (PMDF V4.2-13 #2603) id <01H459SXOEU8000JD9@INFOODS.UNU.EDU>; Fri, 15 Oct 1993 16:22:41 EDT
Date: Fri, 15 Oct 1993 16:22:40 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: John C Klensin <KLENSIN@infoods.unu.edu>
Subject: Re: Character set issues again
In-Reply-To: <9310151544.AA27195@blacks.jpl.nasa.gov>
To: dank@blacks.jpl.nasa.gov
Cc: ietf-wnils@ucdavis.edu, dank@alumni.caltech.edu, Erik Huizer <Erik.Huizer@surfnet.nl>, jkrey@isi.edu
Message-Id: <750716560.544432.KLENSIN@INFOODS.UNU.EDU>
X-Envelope-To: ietf-wnils@UCDAVIS.EDU
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET="US-ASCII"
Content-Transfer-Encoding: 7bit
Mail-System-Version: <MultiNet-MM(330)+TOPSLIB(156)+PMDF(4.2)@INFOODS.UNU.EDU>
Dan,
(1) We very much want to arrive at a solution for non-ASCII character
set issues that is as internet-wide as possible. Adopting one
standardized and recommended solution for wnlis and another for, e.g.,
FTP or MIME would lead us into a Big Mess, to put it mildly.
(2) As you presumably know, the code set of UNICODE is identical to the
code set of the initial plane of ISO International Standard 10646, the
so-called Basic Multilingual Plane (BMP). However, the conclusion of
the relevant international committees has been that BMP (Unicode) alone
is insufficient to handle several important languages in critical
contexts, notably some of the Asian ideographic languages.
(3) A WG is in the process of being defined and created to deal with
these issues across applications. It will not meet in Houston, but can
be expected to meet in Seattle. A mailing list is now available on
which these, and other, cross-applications character issues are
discussed:
Subscribe to: ietf-charsets-request@innosoft.com
or send mail to mailserv@innosoft.com containing the one body
line:
subscribe ietf-charsets
Postings to: ietf-charsets@innosoft.com
(4) As a consequence of the above, while wnils can "officially endorse"
whatever it likes, this issue is out of its scope of work.
John Klensin
Co-Area Director for Applications
- Character set issues again dank
- Re: Character set issues again Peter Deutsch
- Re: Character set issues again John C Klensin