From xemacs-m  Mon Jan 27 18:13:46 1997
Received: from mecca.spd.louisville.edu (mecca.spd.louisville.edu [136.165.40.148])
          by xemacs.org (8.8.4/8.8.4) with SMTP
	  id SAA20677 for <xemacs-beta@xemacs.org>; Mon, 27 Jan 1997 18:13:45 -0600 (CST)
Received: (from tjchol01@localhost) by mecca.spd.louisville.edu (950413.SGI.8.6.12/950213.SGI.AUTOCF) id TAA25796; Mon, 27 Jan 1997 19:13:47 -0500
Date: Mon, 27 Jan 1997 19:13:47 -0500
Message-Id: <199701280013.TAA25796@mecca.spd.louisville.edu>
From: "Tomasz J. Cholewo" <tjchol01@mecca.spd.louisville.edu>
To: xemacs-beta@xemacs.org
Subject: Re: odd charset ISO-2022-INT-1
Mime-Version: 1.0 (generated by tm-edit 7.100)
Content-Type: text/plain; charset=US-ASCII

> A recent xemacs-beta message contained these headers:
>
> Mime-Version: 1.0 (generated by tm-edit 7.100)
> Content-Type: text/plain; charset=ISO-2022-INT-1
>
> This message exposed a bug in VM's MIME display code, which I've
> fixed, but it raised another question.  What is ISO-2022-INT-1,
> and is it really usable as a MIME charset?

Hi,

It was my message.  I wrote it in 20.0-b92 --with-mule.  I noticed this
strange charset after sending it, but I didn't think twice about it.

After `xemacs -q' and `(require 'mime-setup)' the sequence of require
commands goes like this:

mime-setup -> tm-setup -> tm-view -> tm-def -> tl/emu.el -> tl/emu-x20.el

The last file does: (defvar default-mime-charset 'iso-2022-int-1).
Apparently it is an internet standard in draft stage.  I found it at:

http://www.csl.sony.co.jp/person/demizu/apng-i18n/id/draft-ohta-text-encoding-01.txt

Said all that I don't know how to reproduce this header.

Tom

