Mule

Mule requires the w3 lisp package in order to be used as a web browser. Mule version 19.x will not display inline graphics. Xemacs 19.x will display inline graphics, but will not display Japanese. Version 20.0 of xemacs supports both inline graphics and Japanese. You can read about the Emacs-w3 package inclusing information on how to get it at http://pearl.scphys.kyoto-u.ac.jp/comp-doc/mule/w3_toc.html or at the more general <http://www.cs.indiana.edu:80/elisp/w3/docs.html> http://www.cs.indiana.edu:80/elisp/w3/docs.html site which includes information about Emacs-W3 3.0.

Mule is usable as a web browser in text only form. Mule, lynx, and modified Netscape are the only browsers I know of that can display Japanese forms and input Japanese text into the form.

Mule doing a Japanese search on Yahoo Japan

Web Browsing Hints with Mule

Mule under X-Windows works great. However, I've had problems configuring the faces properly. The faces allows different text colors for links, headings, and other text properties. Because of this some of the links on my favorite sites are unreadable. To get around this I've recently switched to mule running in a kterm. This is the command I use in my .fvwmrc file:

kterm -ls -sb -fn 8x16 -fk kanji16 -cr pink -geometry 85x30+9+0 -e mule -nw &

Explanation of options:

• -ls login shell. Read .login or .profile
• -b add scroll bar
• -fn 8x16 set ASCII font size
• -fk kanji16 set Kanji font size
• -cr pink make cursor pink
• -geometry 85x30+9+0 place mule right above my good stuff bar
• -e mule -nw start mule in the kterm and not in the mule window

Mojibake

Mojibake is a Japanese word that refers to screen garbage as a result of the control codes in the Japanese text not being interpretted properly. In an editor this might occur if the editor does not interpret the JIS, ShiftJIS, or EUC Japanese encoding method properly. In a Japanese browser such as mule w3, this can also occur when it fails to interpret JavaScript, frames, or font colors colors properly. I've found that pressing gto reload the screen often solves this problem.