> - Japanese input methods need user preference configuration. > For example, some (not small part of) Japanese people want > Ctrl+U to be Hiragana conversion, Ctrl+I to be Katakana > conversion, Ctrl+O to be Hankaku conversion, Ctrl+P to be > Alphabet conversion (reverse romaji/kana conversion), without > Kakutei (determination). These key bindings are from popular > commercial input engine "ATOK". (It is my first input engine > in 15 years ago for about 8 years. After that, I configured > all input methods (other than SKK) to ATOK-like key binding.)
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 > Are there any Japanese member in Im-ja developers? Japanese > people know many tiny but important points for to achieve > convenient input method and user interface. I agree. For the moment, im-ja seems to be a primarily a convenient way to get Japanese input into a running gtk2 application without logging into a full Japanese locale, or using the command line to manually launch XIM servers, set variables, etc. 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. -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
