From: gabor <ga...@z1...> - 2004-08-27 17:18:50
|
hi, i am learning japanese, and trying to use uim with it... xim works, but for that i need to set up a japanese locale (i use uim- anthy). but i found that mlterm can use uim. can he use it directly (without xim?)? i tried...and cannot turn it on :) uim is activated with left-windows-key + space (Hyper + space in uim config file) but i cannot activate it in mlterm. so: how is uim 'integrated' into mlterm? thanks a lot -- gabor <ga...@z1...> |
From: Seiichi S. <ss...@sh...> - 2004-08-27 21:22:44
|
Hi gabor, On Fri, Aug 27, 2004 at 07:23:01PM +0200, gabor wrote: > but i found that mlterm can use uim. > can he use it directly (without xim?)? Yes, mlterm (in the latest cvs) can use uim without uim-xim bridge. > i tried...and cannot turn it on :) > > uim is activated with left-windows-key + space > (Hyper + space in uim config file) > > but i cannot activate it in mlterm. You may need to recompile mlterm with '--enable-uim' For native uim support as below. $ make clean $ ./configure --enable-uim --OTHER-YOUR-FAVORITE-OPTIONS $ make # make install (as root) How to specify input method: uim with anthy engine $ mlterm --im=uim:anthy XIM with default XIM server $ mlterm --im=xim XIM with xcin on the current locale. $ mlterm --im=xim:xcin XIM with Ami on ko_KR.eucKR locale. $ mlterm --im=xim:Ami:ko_KR.eucKR Or add the following line into ~/.mlterm/main or <PREFIX>/etc/mlterm/main input_method = uim:anthy Also, you can dynamically change the input method and/or the conversion engine via external configuration tools such as mlconfig and mlterm-menu. > so: how is uim 'integrated' into mlterm? as loadable module. BTW, my TODO list for input method is: - rewrite the framework (I'm working for) - write documentations (not written yet) - iiimf support (help) Regards, -- Seiichi |
From: gabor <ga...@z1...> - 2004-08-28 06:03:40
|
On Sat, 2004-08-28 at 06:22 +0900, Seiichi SATO wrote: > Hi gabor, > > > but i found that mlterm can use uim. > > can he use it directly (without xim?)? > > Yes, mlterm (in the latest cvs) can use uim without uim-xim bridge. > > > i tried...and cannot turn it on :) > > > > uim is activated with left-windows-key + space > > (Hyper + space in uim config file) > > > > but i cannot activate it in mlterm. > , > thanks for the help... now it works, but: if i tell uim to use control+space as the hotkey, then it works. but if i tell uim to use left-windows-key+space (hyper+space in uim's config files), then it simply does not work.... any ideas why? -- gabor <ga...@z1...> |
From: Seiichi S. <ss...@sh...> - 2004-08-28 17:43:29
|
On Sat, Aug 28, 2004 at 08:07:54AM +0200, gabor wrote: > if i tell uim to use control+space as the hotkey, then it works. > but if i tell uim to use left-windows-key+space (hyper+space in uim's > config files), > then it simply does not work.... any ideas why? Fix has been committed to cvs just now. At this change, the conversion from X modifier key to uim key became the same as uim-xim and uim's immodule for gtk. Mod1 -> Alt Mod2 -> Meta Mod3 -> Super Mod4 -> Hyper Personally I think that this hard-coded mapping is not good, because modifier key mapping can be changed by xmodmap(1). Probably uim developers already understand it. Anyway, please retry the latest cvs version. Thanks for your report. -- Seiichi |
From: gabor <ga...@z1...> - 2004-08-29 19:28:55
|
On Sun, 2004-08-29 at 02:43 +0900, Seiichi SATO wrote: > On Sat, Aug 28, 2004 at 08:07:54AM +0200, > gabor wrote: > > > if i tell uim to use control+space as the hotkey, then it works. > > but if i tell uim to use left-windows-key+space (hyper+space in uim's > > config files), > > then it simply does not work.... any ideas why? > > Fix has been committed to cvs just now. At this change, the > conversion from X modifier key to uim key became the same as > uim-xim and uim's immodule for gtk. > > Mod1 -> Alt > Mod2 -> Meta > Mod3 -> Super > Mod4 -> Hyper > > Personally I think that this hard-coded mapping is not good, > because modifier key mapping can be changed by xmodmap(1). > Probably uim developers already understand it. > > Anyway, please retry the latest cvs version. thanks a lot...now it works nicely.. well, i had to select uim instead of xim in the menu, and select the correct uim input module. then it was ok ;) thanks, gabor |
From: gabor <ga...@z1...> - 2004-08-29 20:11:03
|
On Sun, 2004-08-29 at 21:33 +0200, gabor wrote: > On Sun, 2004-08-29 at 02:43 +0900, Seiichi SATO wrote: > > On Sat, Aug 28, 2004 at 08:07:54AM +0200, > > gabor wrote: > > > > > if i tell uim to use control+space as the hotkey, then it works. > > > but if i tell uim to use left-windows-key+space (hyper+space in uim's > > > config files), > > > then it simply does not work.... any ideas why? > > > > Fix has been committed to cvs just now. At this change, the > > conversion from X modifier key to uim key became the same as > > uim-xim and uim's immodule for gtk. > > > > Mod1 -> Alt > > Mod2 -> Meta > > Mod3 -> Super > > Mod4 -> Hyper > > > > Personally I think that this hard-coded mapping is not good, > > because modifier key mapping can be changed by xmodmap(1). > > Probably uim developers already understand it. > > > > Anyway, please retry the latest cvs version. > thanks a lot...now it works nicely.. > > well, i had to select uim instead of xim in the menu, > and select the correct uim input module. > then it was ok ;) well, not that nicely :(( problem: i start mlterm with someting like: mlterm --type=xft and activate uim. now i enter "watashi" i get 3 squares. i press <space>, i get 1 square i press <enter>, i get the correct 私 symbol. or: i enter "watashi" i get 3 squares. i press <enter>, i get "わたし" so, basically when the symbols are running "inside" uim, i cannot see them. but then when i press <enter>, and they get back to mlterm, i can see them correctly. btw i still cannot make --type=xcore display japanese fonts..can this be somehow related to this problem? thanks, gabor |
From: Seiichi S. <ss...@sh...> - 2004-08-29 21:24:30
|
On Sun, Aug 29, 2004 at 10:15:22PM +0200, gabor wrote: > problem: > > i start mlterm with someting like: > mlterm --type=xft > > and activate uim. > > now i enter "watashi" > i get 3 squares. > i press <space>, i get 1 square > i press <enter>, i get the correct 私 symbol. > > or: > i enter "watashi" > i get 3 squares. > i press <enter>, i get "わたし" > > so, basically when the symbols are running "inside" uim, > i cannot see them. > but then when i press <enter>, and they get back to mlterm, > i can see them correctly. That is a bug. When mlterm with uim and japanese conversion engine are running in UTF-8, mlterm requires fonts for japanese character set. preedit and candidate strings are encoded in EUC-JP(native encoding of conversion engine). Please specify fonts for JISX0208_1978, JISX0208_1983 and JISX0208_1990 in .mlterm/*font. In the future, this problem will be fixed. Thanks for your report, again. -- Seiichi |
From: Seiichi S. <ss...@sh...> - 2004-09-07 17:27:10
|
On Mon, Aug 30, 2004 at 06:24:08AM +0900, Seiichi SATO wrote: > When mlterm with uim and japanese conversion engine are running > in UTF-8, mlterm requires fonts for japanese character set. > preedit and candidate strings are encoded in EUC-JP(native > encoding of conversion engine). [...] > In the future, this problem will be fixed. fixed in cvs. -- Seiichi |