From xemacs-m  Sat Feb 15 16:27:03 1997
Received: from venus.Sun.COM (venus.Sun.COM [192.9.25.5])
	by xemacs.org (8.8.5/8.8.5) with SMTP id QAA08854
	for <xemacs-beta@xemacs.org>; Sat, 15 Feb 1997 16:27:03 -0600 (CST)
Received: from Eng.Sun.COM ([129.146.1.25]) by venus.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id BAA02023; Thu, 13 Feb 1997 01:13:37 -0800
Received: from kindra.eng.sun.com by Eng.Sun.COM (SMI-8.6/SMI-5.3)
	id BAA06612; Thu, 13 Feb 1997 01:13:36 -0800
Received: from xemacs.eng.sun.com by kindra.eng.sun.com (SMI-8.6/SMI-SVR4)
	id BAA26496; Thu, 13 Feb 1997 01:13:34 -0800
Received: by xemacs.eng.sun.com (SMI-8.6/SMI-SVR4)
	id BAA05278; Thu, 13 Feb 1997 01:13:30 -0800
Date: Thu, 13 Feb 1997 01:13:30 -0800
Message-Id: <199702130913.BAA05278@xemacs.eng.sun.com>
From: Martin Buchholz <mrb@Eng.Sun.COM>
To: Oscar Figueiredo <Oscar.Figueiredo@di.epfl.ch>
Cc: Jeff Miller <jmiller@bay1.bayserve.net>,
        beta-list <xemacs-beta@xemacs.org>
Subject: Re: iso-2022
In-Reply-To: <9702120852.AA17900@lspsun16.epfl.ch>
References: <Pine.SUN.3.95.970211233001.27642A-100000@bay1.bayserve.net>
	<9702120852.AA17900@lspsun16.epfl.ch>
Reply-To: Martin Buchholz <mrb@Eng.Sun.COM>
Mime-Version: 1.0 (generated by tm-edit 7.100)
Content-Type: text/plain; charset=US-ASCII

>>>>> "Oscar" == Oscar Figueiredo <Oscar.Figueiredo@di.epfl.ch> writes:

Oscar> [1  <text/plain; us-ascii (7bit)>]
>>>>> "Jeff" == Jeff Miller <jmiller@bay1.bayserve.net> writes:

Jeff> If I use vm under mule, I should get Japanese chars when mail is
Jeff> from MORIOKA Tomohiko, right?  Assuming I had a ISO-2022 font installed
Jeff> right?

Oscar> Ensure you're using a non-european language environment.

Oscar> (set-language-environment nil)

Oscar> then quit VM and re-launch it, it should work fine. If not, try
Oscar> upgrading to tm-vm 8.9 (attached to this message as it hasn't been
Oscar> released in tm yet). It works fine for me.

(based on experience with tm-vm 7)

You can get Japanese characters to appear in VM + tm-vm 7 when you
have done (set-language-environment) appropriately, but this is really
just an accident - two wrongs appearing to be a right.

When the message is initially read in (crashbox) the message is
converted.  This is wrong.  The message should be read in and stored
in raw mode (binary or no-conversion).  When the message is displayed
in the *Preview-inbox* buffer, tm-vm should be doing MIME conversion
based on MIME headers, or if those are not present, the current
language environment.  Because 2 things are done wrong, they `cancel'
and the user appears to get the characters correctly.  But the damage
becomes more obvious after VM is exited, the folder is saved, and VM
is started again - then the mail message is likely to be corrupted.

Martin

