Only in, I'm having es_ES deadkey problems.

eculp eculp at
Sat Nov 29 06:37:59 PST 2008

Quoting Nikola Lečić <nikola.lecic at>:

> Hash: RIPEMD160
> On Fri, 28 Nov 2008 18:29:36 -0600
> eculp <eculp at> wrote:
>> I didn't even realize that there were multiple input methods from a
>> laptop keyboard.  Smart Common Input Method, I doubt because it
>> doesn't seem to be very smart.
>> Openoffice is the only program that has any problems. Skype, pidgen,
>> term windows, Konsole, even gimp work perfectly.
> So you use some Spanish keyboard with one of the SCIM IMEngines? If
> this is so, then you probably have something like this in your
> environment:
>   GTK_IM_MODULE=scim

I had neither in my environment so I added them and there was a  
change.  The dead keys printed correctly but weren't dead.  The same  
with xim.  I am seeing this on different laptops and one multiple  
desktop keyboards.  They are all runing KDE and the desktops are  
running FreeBSD 7.1-PRERELEASE and the laptop uptodate Current.

> Please try GTK_IM_MODULE=xim. Switching among keyboards will be a bit
> harder (SCIM keyboard icon and the actual keyboard will sometimes be
> desynchronised when you change focus among windows), but this used to
> solve deadkeys problem for me in the past.
> If this doesn't help, you can try textproc/scim-bridge with
> GTK_IM_MODULE=scim-bridge.
> Although I must add that the problem mainly disappeared when I switched
> to (currently running 3.1.20081024).

I'm going to give it a try because we have been using openoffice since  
1.x without problems and without having to learn about SCIM ;)


> - --
> Nikola Lečić = Никола Лечић
> fingerprint : FEF3 66AF C90E EDC3 D878  7CDC 956D F4AB A377 1C9B

> Version: GnuPG v2.0.9 (FreeBSD)
> iJwEAQEDAAYFAkkxRgAACgkQ/MM/0rYIoZhNtAP9GNcqnMOA66cmzd0TZUeCggyd
> QjXx7sAZJG0J9+OiyMRS1gJZKZ5EhZZ2wdhtUzEHXr4/oX+/LbLPZaq7/azsGpD/
> LF5Qg2IWjArV+28EXWxhUC0yCcQnNLwSa/Jmn7AuN6fFjxbC3VEwgAzw9qov8HXG
> 3PlXeIz6Z18jJ/9BR+4=
> =oR6t

More information about the freebsd-ports mailing list