Use `apt-get' to install the following Debian packages. You can probably use dpkg or dselect or other Debian package managers that are becoming available, but I used apt-get which takes care of many of the dependencies for you. If you use others (such as raw dpkg) the dependencies may need to be satisfied (of course Debian won't actually let you install packages with broken dependencies so you won't mess up your system. You will just have to get hold of all the necessary debs first). Using dselect+ftp should work well also (if you can stand dselect).
kterm -km sjis &This will start kterm using the `sjis' kanji mode. You only need this option if you intened to use mule inside the kterm.
enable-alternate-editor-implicitly(this last is optional. If you don't enable it implicitly you must explicitly type C-_ to start the editor). Also set
character-setto ``iso-2022-jp'' and
editorto ``mule'' (if you made the symlink as I did above, otherwise, set it to ``xemacs-21.1.10-mule-canna-wnn'' or however the current Debian xemacs-mule package gets installed into /usr/bin. You can look at /usr/local/bin/mule to see if the symlink is in place.)
You can also read Japanese text outside of pine by using
less -r [file]inside a kterm.
To write Japanese mail, start composing in Pine as usual, then either implicitly start mule by moveing below the headers in Pine's compose window, or explicitly by hitting ^_ (control-underscore).
When mule starts up, hit C-\ (control-backslash). You will be prompted for an ``Input method''. Use ``japanese-canna''. Then enter Japanese by type by entering romanji and using space-bar and arrow keys to find which kanji you want. Hit enter when satisfied or C-g a few times to cancel. After hitting enter the fences (``|...|'') will disappear. Also, when you enter romanji, it will be translated to hiragana. If you hit the down arrow just after the hiragana shows up you will get katakana. You may need to do `M-x setup-japanese-canna' to get the fonts looking right. If this is necessary, you can put `(setup-japanese-canna)' in your .emacs file to make this default.
After finishing the composing exit mule as normal (C-x C-c y) and the message will be put into Pine's ``Message Text'' buffer. It will look like garbage line noise because Pine doesn't seem to know what type of encodeing this is (maybe a pico problem). If anyone knows the solution to this, please email me. But, it is actually okay (mail yourself a few test emails to check it).
Finally do C-x to send as usual.
xset fp+ tcp/server:port/catalogsee below for local example. When you first load fonts it can take a while and it may appear that the system is hung. Just be patient.
myhost> ssh ale
ale> kterm -km sjis &
xset fp+ tcp/ale.physics.sunysb.edu:7100/allFinally, configure your Pine as above and you should be all set.