[oe] Problem with i18n (input)

[Otavio Salvador]

Phil Blundell <pb at reciva.com> writes:

> On Mon, 2008-06-30 at 17:02 -0300, Otavio Salvador wrote:
>> When I press "'e" it gives me nothing. When I run it inside xev it
>> gives me:
>> 
>> KeyPress event, serial 30, synthetic NO, window 0x1400001,
>>     root 0x3a, subw 0x0, time 3675299458, (149,171), root:(572,473),
>>     state 0x0, keycode 34 (keysym 0xfe51, dead_acute), same_screen YES,
>>     XLookupString gives 1 bytes: (b4) "�"
>>     XFilterEvent returns: False
>> 
>> KeyRelease event, serial 30, synthetic NO, window 0x1400001,
>>     root 0x3a, subw 0x0, time 3675299519, (149,171), root:(572,473),
>>     state 0x0, keycode 34 (keysym 0xfe51, dead_acute), same_screen YES,
>>     XLookupString gives 1 bytes: (b4) "�"
>>     XFilterEvent returns: False
>> 
>> KeyPress event, serial 30, synthetic NO, window 0x1400001,
>>     root 0x3a, subw 0x0, time 3675302404, (149,171), root:(572,473),
>>     state 0x0, keycode 26 (keysym 0x65, e), same_screen YES,
>>     XLookupString gives 1 bytes: (65) "e"
>>     XFilterEvent returns: False
>> 
>> KeyRelease event, serial 30, synthetic NO, window 0x1400001,
>>     root 0x3a, subw 0x0, time 3675302404, (149,171), root:(572,473),
>>     state 0x0, keycode 26 (keysym 0x65, e), same_screen YES,
>>     XLookupString gives 1 bytes: (65) "e"
>>     XFilterEvent returns: False
>
> This output means that XIM isn't enabled and hence you aren't getting
> any compose handling at the Xlib level.  That shouldn't matter in your
> case, though, because GTK does its own compose handling and XIM is
> basically just dead weight.

Any way for me to enable it?

> If you see nothing at all when you type "'e" then that would suggest
> that GTK is correctly interpreting the dead key and generating the right
> keycode internally, but that something is then going wrong after that.
> (If it didn't understand the dead acute at all then you would see a
> plain unadorned "e".)

Humm, confusing ...

> Unfortunately I don't think there is any convenient xev equivalent that
> will show you gtk's inner workings, so you might have to resort to the
> debugger to figure out what's going on here.  I do have a vague
> recollection from when I last worked on this stuff that gtk was quite
> sensitive to locale settings.  Presumably locale-base-pt-br is a UTF8
> locale, right?  Do you have "LANG=pt_BR" set in your environment?

Yep .. I've used: LC_ALL=pt_BR.

-- 
        O T A V I O    S A L V A D O R
---------------------------------------------
 E-mail: otavio at debian.org      UIN: 5906116
 GNU/Linux User: 239058     GPG ID: 49A5F855
 Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
 you the whole house."