From xemacs-m  Tue Dec 10 00:57:05 1996
Received: from venus.Sun.COM (venus.Sun.COM [192.9.25.5]) by xemacs.cs.uiuc.edu (8.8.3/8.8.3) with SMTP id AAA22225 for <xemacs-beta@xemacs.org>; Tue, 10 Dec 1996 00:57:04 -0600 (CST)
Received: from Eng.Sun.COM ([129.146.1.25]) by venus.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id WAA05936; Mon, 9 Dec 1996 22:56:37 -0800
Received: from kindra.eng.sun.com by Eng.Sun.COM (SMI-8.6/SMI-5.3)
	id WAA26734; Mon, 9 Dec 1996 22:56:34 -0800
Received: from xemacs.eng.sun.com by kindra.eng.sun.com (SMI-8.6/SMI-SVR4)
	id WAA11898; Mon, 9 Dec 1996 22:56:33 -0800
Received: by xemacs.eng.sun.com (SMI-8.6/SMI-SVR4)
	id WAA21344; Mon, 9 Dec 1996 22:56:32 -0800
Date: Mon, 9 Dec 1996 22:56:32 -0800
Message-Id: <199612100656.WAA21344@xemacs.eng.sun.com>
From: Martin Buchholz <mrb@Eng.Sun.COM>
To: wmperry@aventail.com
Cc: xemacs-beta@xemacs.org, w3-beta@indiana.edu
Subject: Equivalent of *noconv* under old Mule in XEmacs 20.0
In-Reply-To: <199612091721.JAA22509@newman>
References: <199612091721.JAA22509@newman>
Reply-To: Martin Buchholz <mrb@Eng.Sun.COM>
Mime-Version: 1.0 (generated by tm-edit 7.94)
Content-Type: text/plain; charset=US-ASCII

>>>>> "Bill" == William Perry <wmperry@aventail.com> writes:

Bill> Subject says it all.  What is the appropriate 'null' conversion type?
Bill> Also, anybody out there want to help get real internationalization support
Bill> done in Emacs-W3 sometime soon?  ie: Get charset information out of the
Bill> MIME headers and have some sort of mapping to mule character sets?  I'd
Bill> really appreciate the help.

There has been a massive name change of charsets to be compatible with
a future Emacs/Mule release.

(charset-list)  ==>

(chinese-cns11643-6 chinese-cns11643-3 korean-ksc5601 chinese-big5-2
japanese-jisx0212 latin-jisx0201 latin-iso8859-9 arabic-iso8859-6
latin-iso8859-3 control-1 arabic-1 chinese-cns11643-7
chinese-cns11643-4 ipa chinese-cns11643-2 chinese-big5-1
japanese-jisx0208 katakana-jisx0201 hebrew-iso8859-8
cyrillic-iso8859-5 latin-iso8859-2 ascii arabic-0 sisheng
vietnamese-upper chinese-cns11643-5 vietnamese-lower ethiopic
composite chinese-cns11643-1 chinese-gb2312 japanese-jisx0208-1978
thai-tis620 greek-iso8859-7 latin-iso8859-4 latin-iso8859-1 arabic-2)

Bill> Also - how to handle different encodings within a single buffer?  Is that
Bill> even possible or desirable?  I'm going to have to snag the last HTTP/1.1
Bill> draft and give it a read tonight.

TM is the best source of code to read for the kinds of conversions
you'll be doing.  All charsets can be simultaneously present in a
buffer.  For multiple character sets to be present in an external
input, either file or process input, a coding system that supports
multiple languages needs to be used - primarily ISO2022-based ones.
The lisp/mule/*.el files in the XEmacs distribution contain
iso2022-encoded characters in several different languages.

Martin

