From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from drizzle.Stanford.EDU ([36.59.0.16]) by hawkwind.utcs.utoronto.ca with SMTP id <23982>; Mon, 7 Nov 1994 16:42:45 -0500
Received: from hassle.Stanford.EDU (hassle.Stanford.EDU [36.59.0.161]) by drizzle.Stanford.EDU (8.6.8/8.6.4) with ESMTP id NAA01925 for <sam-fans@hawkwind.utcs.toronto.edu>; Mon, 7 Nov 1994 13:42:17 -0800
From:	Castor Fu <castor@drizzle.Stanford.EDU>
Received: (castor@localhost) by hassle.Stanford.EDU (8.6.8/8.6.4) id NAA01283 for sam-fans@hawkwind.utcs.toronto.edu; Mon, 7 Nov 1994 13:44:32 -0800
Message-Id: <199411072144.NAA01283@hassle.Stanford.EDU>
Subject: Japanese input and Sam
To:	sam-fans@hawkwind.utcs.toronto.edu
Date:	Mon, 7 Nov 1994 16:44:31 -0500
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Has anyone hacked japanese input methods into 'sam'?  

If I were to do this, what I would probably do is mash a tcl interpreter
into libXg and handle the input translations in tcl.  Then the code
in 'latin1.c' would be moved into an area which could be edited without
recompiling sam.

I suppose purists would feel this was sacreligious, but when using a large
character set like Unicode, I think having hard coded tables like
sam uses is sort of silly.

	-castor