Re: tlug: Japanese input systems

[Craig Oda <craig@example.com>]

On Tue, 25 Nov 1997, Stephen J. Turnbull wrote:

Stephen,
thank you for the explanation.  I'm starting to get a grasp of
this slowly.  I'm expecting that it will take time, but feel
that I'm making some progress.  For example, in thinking how
kinput2 talks to kterm, I managed to input kanji on a remote
UNIX system's mule through a telnet session.  The way I did
this was by specifying 

   $ telnet -L twics.com

inside of the kterm on my Linux box.  The -L flag specifies
8-bit output.  I wonder if telnet uses 8-bit for input by
default?  How else could the EUC characters get from kinput2
safely to mule on the remote system?

I'll probably ask you a few questions when we meet F2F.


turnbull>XIM is a general protocol for allowing FEPs and BEPs to talk to an
turnbull>app.  Using XIM allows you to interchange both apps and B/FEPs.
turnbull>Kinput is a specific protocol that allows any conforming app to talk
turnbull>to kinput2.

Here is what I thought about XIM, correct me if needed.  XIM was
standardized in X11R6, which became available for Linux around
late 1994 or 1995.  I remember the switch from XConfig to XF86Config.
Aside from being a bit faster, it appears that the internationalization
support is better than in X11R5.  Now, I remember that we had a
discussion about XIM with XEmacs 20.0 and you did a modification
to allow its use.  Does this mean that XIM is still not that widely
used and that things like kinput2 are still used?  Also, in X11R5,
weren't Xsi and Ximp used and kind of replaced by XIM in the X11R6
standard?

I'm starting to think that in order to understand XIM more, I 
may have to look at how it interacts with Xlib.

turnbull>delegate (3) to a dictionary server.  The XIM protocol is embedded in
turnbull>Xlib.  The Kinput protocol must be programmed "by hand" in each app.

So, XIM protocol  is kind of an X standard way to do it and maybe kinput
protocol
was an earlier development that is being obsoleted by XIM protocol?

turnbull>protocol.  There is not a single KKTP; Canna, SJ3, skkserv, and Wnn
turnbull>all have their own.  The KKTP is typically embodied in a library such
turnbull>as libwnn or libcanna.  Many input methods also provide help with (2), 
turnbull>assembling the keystrokes into a dictionary key; Canna's libRK is an

This is what I thought too.  So, I guess it is okay to refer to the
Canna Protocol and the Wnn Protocol.  In order to use the Canna Protocol
I would use an application that uses libcanna.  

turnbull>Hope this helps.

Thanks.  :-)

Regards,
Craig



--------------------------------------------------------
"Knowledge is the air and light of civilization.  Transform it and you
transform all else."
Craig Oda 	craig@example.com	
   TWICS - IEC Building, 1-21 Yotsuya, Shinjuku-ku, Tokyo 160 JAPAN
Main Reception: 03-3351-5977	Fax: +81-3-3353-6096

---------------------------------------------------------------
TLUG Meeting Dec. 13, 12:30 at Tokyo station Yaesu Chuo ticket gate
13:30 Starbuck's coffee.  13:45 HSBC | info: joem@example.com
At least 3 functional Sparc IPC machines will be raffled out
---------------------------------------------------------------
a word from the sponsor:
TWICS - Japan's First Public-Access Internet System
www.twics.com  info@example.com  Tel:03-3351-5977  Fax:03-3353-6096