Re: bug: set-terminal-coding-system doesn't work?

Kazz> "T. Kurosaka - Sun Professional Services" Kazz> <kuro(a)Japan.Sun.COM&gt; writes: Kazz> It doesn't matter of terminal emulator but input method, Kazz> doesn't it? Well, no. There are several ways that this can be implemented. (1) shelltool is XIM-enabled, filters everything, and sees only the events XIM chooses to give it. It passes Japanese to the app. Diagnosis: input method problem. (2) shelltool looks at the events and decides what to pass to XIM. It passes Japanese to the app. Diagnosis: shelltool or input method. (3) No XIM, but shelltool connects directly to an input server. It passes Japanese to the app. Diagnosis: shelltool, input method, or app may be confused. (4) No XIM in shelltool, which thinks it's passing a TTY representation of the keystrokes to the app, which actually implements XIM which steals the keystrokes. (I don't think this actually ever happens, as it would require a keyboard grab by the input server. Abomination. But that's the way that FEPs are implemented in DOS/Windose, at least up to 1994 or so.) Diagnosis: App or input method problem. (5) No XIM in shelltool, which passes a TTY representation of the keystrokes to the app, which directly connects to a henkan server. Diagnosis: App or input method problem. And of course all of these can be implemented as alternatives, as in XEmacs. I have no idea what the problem is, since I know nothing about the various tools (except XEmacs). If XIM weren't so buggy, consistently using it would make debugging a lot easier ;-) -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 __________________________________________________________________________ __________________________________________________________________________ What are those two straight lines for? "Free software rules."