Re: atypical compose key
- From: Andriy Gapon <avg icyb net ua>
- To: Etsushi Kato <ek kato gmail com>
- Cc: gtk-i18n-list gnome org
- Subject: Re: atypical compose key
- Date: Thu, 28 Sep 2006 18:01:20 +0300
on 28/09/2006 17:34 Etsushi Kato said the following:
> On 9/28/06, Andriy Gapon <avg icyb net ua> wrote:
[snip]
>> I believe that this is a check for a current key being pressed while
>> some modifier key is held down and I think that Ctrl and Alt are always
>> in the default modifier mask (Shift is explicitly ignored in this check).
>
> Right. One way to solve this problem is using input method framework
> using key snooper (like SCIM), or using toplevel event (like uim),
> which can be used with GTK_IM_MODULE=XXX (name of input method) if you
> installed them. These input method uses internal Compose sequences
> instead of (before) gtkimcontextsimple.
Etsushi,
thank you for the reply.
I've actually tried to play with IMs but without much luck. I think I
understand the concept behind IMs/XIM, but practical usage is hard to
get. Also, I don't need to input any CJK stuff and I only use cyrillic
and extended latin input (Eastern, Central and Western European
languages), so using some powerful IM seems like an overkill to me.
Besides, currently I can input everything I want by running Vim in xterm
— standard modern xfree86/x.org facilities and UTF-8 locale are
sufficient for me.
Thus, the following question: is there any way to tell/trick GTK
application to not use all the wonderful input processing it has, nor
any sophisticated external IM, and simply (and fully) obey X, just the
same way xterm does ? [This also includes using X Compose sequences
instead of those hardcoded into GTK, etc]
[snip]
>> Obviously such a change would make me (and maybe couple of other
>> fellows) happy. And I don't think that it will break anything for
>> anybody as it seems highly unlikely that someone would define something
>> like <Alt>+<Compose> as a GNOME accelerator key. But of course this
>> might still be possible.
>>
>> What do you guys think ?
>
> I don't think this cause any problem on accelerated keys. These event
> is treated before gtkimcontextsimple AFAIF, but I may be wrong.
--
Andriy Gapon
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]