[Uim-bugs] [Bug 8118] UIM 1.2.x breaks Compose key input

[bugzilla-daemon at annarchy.freedesktop.org]

Please do not reply to this email: if you want to comment on the bug, go to    
       
the URL shown below and enter yourcomments there.     
   
https://bugs.freedesktop.org/show_bug.cgi?id=8118          
     




------- Additional Comments From ekato at ees.hokudai.ac.jp  2006-09-03 21:00 -------
Thanks for the report.

>From uim 1.2.0, our GTK+ and Qt input modules use X11's compose sequence table
in backend compose input instead of gtk+ internal one, as requested in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377808.  The reporter said
GTK+'s internal table is not sufficient for user of traditional X11.

If you use da_DK.UTF-8 locale, $prefix/share/X11/locale/en_US.UTF-8/Compose is
used as a compose table.  And it doesn't seems to have "<Multi_key> <o> <slash>"
sequence as ø letter.  That the problem.

One way to solve the problem is copy
$prefix/share/X11/locale/en_US.UTF-8/Compose as $HOME/.XCompose, and
add your required compose sequences as follows.

<Multi_key> <o> <slash> : "ø" U00F8


Could you tell me which sequences have no effent (you said the vast majority)
with uim-1.2.1?

Cheers,
-- 
Etsushi Kato

          
     
     
--           
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email         
     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.