From xemacs-m  Mon Feb 10 13:38:15 1997
Received: from black-ice.cc.vt.edu (root@black-ice.cc.vt.edu [128.173.14.71])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id NAA12514
	for <xemacs-beta@xemacs.org>; Mon, 10 Feb 1997 13:38:14 -0600 (CST)
Received: from black-ice.cc.vt.edu (valdis@LOCALHOST [127.0.0.1])
	by black-ice.cc.vt.edu (8.8.5/8.8.5) with ESMTP id OAA18956;
	Mon, 10 Feb 1997 14:38:08 -0500
Message-Id: <199702101938.OAA18956@black-ice.cc.vt.edu>
X-Mailer: exmh version 2.0gamma 1/27/96
To: Oscar Figueiredo <Oscar.Figueiredo@di.epfl.ch>
Cc: XEmacs Beta Mailing List <xemacs-beta@xemacs.org>
Subject: Re: State of VM + XEmacs/Mule 
In-Reply-To: Your message of "Mon, 10 Feb 1997 14:42:15 +0100."
             <9702101342.AA15527@lspsun16.epfl.ch> 
From: Valdis.Kletnieks@vt.edu
X-Url: http://black-ice.cc.vt.edu/~valdis/
References: <199702032050.MAA29644@xemacs.eng.sun.com> 
 <9702091254.AA14207@lspsun16.epfl.ch> <199702100724.XAA27151@xemacs.eng.sun.com>
            <9702101342.AA15527@lspsun16.epfl.ch>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_20321214P";
	micalg=pgp-md5; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Mon, 10 Feb 1997 14:38:07 -0500

--==_Exmh_20321214P
Content-Type: text/plain; charset=us-ascii

On Mon, 10 Feb 1997 14:42:15 +0100, you said:
> Subject: (I$r<B9T$9$k(B (I}K!(B

*BZZT* Wrong. Thank you for playing.

This needs to have RFC1522 header encoding around it, something like this:

From: =?ISO-2022-JP?B?GyRCPGkyLBsoQiAbJEJDTkknGyhC?= / MORIOKA Tomohiko 
<morioka@jaist.ac.jp>

Otherwise, the recipeint has *NO* way to know what charset to use
to render it.  My mail reader guessed at ico8859-1 and of course, Lost Big
Time.

> Content-type: text/plain; charset="ISO-2022-JP"
> 
> 
> (I3FJ8;z=89g(B((INc(B
> (I%/%i%$%"%s%H$H$7$F<B9T$9$k$K$O(B

I'm not that strong on how the 2022-JP stuff works, but this may be
missing a Content-Type-Encoding for either Quoted-Printable, or Base64,
whichever is more appropriate for 2022-JP.

Your original message got sent with a CTE of '7bit', which requires that
your data be 7-bit-clean.  I remember that 2022-JP uses escape sequences
to get into Kanji mode - but are said Kanji's 7-bit clean?

-- 
				Valdis Kletnieks
				Computer Systems Engineer
				Virginia Tech



--==_Exmh_20321214P
Content-Type: application/pgp-signature

-----BEGIN PGP MESSAGE-----
Version: 2.6.2

iQCVAwUAMv95HNQBOOoptg9JAQHI+AP/R3DBKzYQ+XyI9syLbXoZOYYit5Y4c1gA
I9khgWPrkgw4ywfUqqNZqLAioRXRZiwBVmvOE/feFWQj7kUEQ/l6Dz3VRwXYb6Ku
QIB/hrGW+uMKTiQMoqmxJTvng3JSUSMshJdKwKsc/yLZDNLIzw4FAbf85IYdA6+2
ThnmNK20MPo=
=nk2H
-----END PGP MESSAGE-----

--==_Exmh_20321214P--

