Hi, From: srintuar26 <[EMAIL PROTECTED]> Subject: Re: gtk2 + japanese; gnome2 and keyboard layouts Date: Mon, 31 Mar 2003 21:27:29 -0500
> Yes, that is a good point, but it brings up a question: > how is this going to interact with applications which already > have meanings for CTRL+O (File Open), CTRL+P (Print), etc Key bindings of Japanese input methods are classified into (at least) three categories: - keys which must be available everytime - keys which must be available only when input method is active - keys which msut be available only when there are undetermined string My examples of CTRL+O and CTRL+P are the third category, because they convert current undetermined strings into Hiragana, Katakana, and so on. In other cases, the input method can pass these key sequences to the application softwares. Only the first category keys are fatal for collision. However, it includes only one key, input method activation (like Shift + Space or Henkan in im-ja). Keys like mode change among Hiragana/Katakana/Kanjipad are the second category in ordinary input methods, though im-ja assignes Shift+Space or Henkan (same to input method activation) for this function. > As a primary input method for a native speaker: I think it > needs pehaps a bit more work, and of course evolution, mozilla, > vim, etc, have to complete their transitions to gtk2. To be popular among native (Japanese) speakers, popular softwares must support GTK2 input methods. For example, mule/emacs/xemacs, kterm, rxvt, xterm, and KDE softwares. Especially, mule/emacs/xemacs is overwhelmingly popular among Japanese because it has been the only way to write Japanese in both of X and non-X environments for tens of years. --- Tomohiro KUBOTA <[EMAIL PROTECTED]> http://www.debian.or.jp/~kubota/ -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
