From xemacs-m  Fri Feb  7 01:56:20 1997
Received: from pentagana.sonic.jp (root@tokyo-01-045.gol.com [202.243.51.45])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id BAA28629
	for <xemacs-beta@xemacs.org>; Fri, 7 Feb 1997 01:56:18 -0600 (CST)
Received: from mother.sonic.jp (mother.sonic.jp [194.93.1.1]) by pentagana.sonic.jp (8.7.1+2.6Wbeta4/3.4W3) with ESMTP id QAA00342 for <xemacs-beta@xemacs.org>; Fri, 7 Feb 1997 16:53:55 +0900
Received: from pentagana (jhod@[194.93.1.69]) by mother.sonic.jp with SMTP (8.7.1/8.7.1) id QAA15001 for <xemacs-beta@xemacs.org>; Fri, 7 Feb 1997 16:55:16 +0900 (JST)
Sender: jhod@mother.sonic.jp
Message-ID: <32FADF90.79022BAD@po.iijnet.or.jp>
Date: Fri, 07 Feb 1997 16:53:52 +0900
From: Jareth Hein <jhod@po.iijnet.or.jp>
Organization: Sonic Software Planning, Tokyo
X-Mailer: Mozilla 3.01 (X11; I; Linux 2.0.28 i586)
MIME-Version: 1.0
To: XEmacs Beta Mailing List <xemacs-beta@xemacs.org>
Subject: Re: Mule coding systems, SJIS BUG!!!
References: <32F96C53.273F69AD@po.iijnet.or.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Jareth Hein wrote:
> 
> There is a showstopper bug in 20.0 (and has been for a long while, as
> far as I can tell...) involving the SJIS coding system. SJIS
> (Micky$loth's unfortunatly popular bastardization of JISX0201+JISX208)
> data can be read in, auto-detected and properly decided and displayed,
> but when written in SJIS the data is corrupted beyond recovery. The
> following patch fixes an obvious flaw in the code, but even this does
> not remove the problem.
> 
<patch sniped>

> I'm not familiar enough yet with the conversion engine to figure out why
> it is failing, as the rest of the code looks correct to me. Martin?
> 

(gee... I'm getting good at following myself up...)
Excuse my brain-fart. The patch I posted DOES clean up the SJIS problem.
I just somehow managed to screw up my test modules...

--Jareth

