[Fedora-i18n-bugs] [Bug 749497] ibus-gnome3 shows xkb options with empty strings

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=749497

--- Comment #5 from fujiwara <tfujiwar at redhat.com> 2011-11-08 05:36:34 EST ---
(In reply to comment #4)
> Got it, thanks.  But then, if this is the only case, isn't it feasible to track
> group change event (instead of Win-key event) with libxklavior and update the
> menu labels so that all of them look like mono keymaps?  I mean, the first
> keymap is still combined but the menu label looks like mono.

I agree with your point.
Now I'm thinking all ibus keymap engines need to be combined keymaps and
similar behavior with gnome-settings-daemon keyboard GUI. Then I would think
ibus needs to contact libgnomekbd to get the keyboard status.
Also thinking about #2 in the upstream bug comment #51:
https://bugzilla.gnome.org/show_bug.cgi?id=641531#c51
Probably I think ibus needs to have the different UI between GNOME and
non-GNOME due to libgnomekbd.
Probably I think upstream wants to use libgnomekbd simply for gnome3.

For GNOME:
libgnomekbd is used and ibus-xkb won't be used.
ibus keymap engine is combined keymap and can be configured by
gnome-control-center only.

For non-GNOME:
ibus-xkb is used.
ibus keymap engine is mono keymap and can be configured by ibus-setup (will be
ibus-setup-xkb).

Originally I thougut the number of XKB keymaps is limited by four but
technically ibus keymap engine is unlimited. And I implemented the first ibus
keymap engine only is combined keymap.
However probably there would be several problems and complicated.

I'm also thinking probably using libgnomekbd does not need bridge-hotkey
feature.

To detect desktops, I'd think DESKTOP_SESSION by default at the moment.
Using X11 Atom would be complicated, I guess.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.