Comment #2 on issue 1598 by [email protected]: 'Default' XKB layout in ibus
http://code.google.com/p/ibus/issues/detail?id=1598

takao.fujiwara1: I don't understand whether you're suggesting a workaround to us or explaining what you're going to implement in ibus.

Anyway, I also hate how ibus 1.5 completely takes over keyboard layout selection and I'm going to stick with ibus 1.4 until newer ibus versions stop doing that. I don't care whether Ctrl+Space toggles ibus input modes on/off or cycles between multiple input modes as long as: a) One of the modes in the cycle completely passes control over keyboard layout to X server/window manager. I don't want to configure ASCII-based keyboard layouts in ibus, I want to configure them in KDE control center and switch between them using the KDE panel widget. b) ibus uses keyboard layout from X server/window manager for romaji-based input methods. And I don't mean some "default" layout, I mean the active one. When I configure the KDE panel widget to switch between Dvorak, QWERTZ and AZERTY layouts, I want to type romaji using whichever of the three is selected in KDE when I press a key.

ibus 1.4 does both flawlessly so I don't see any reason why that shouldn't be possible in newer versions. And I don't take "write your own system-wide config file" as an answer here.

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
--
You received this message because you are subscribed to the Google
Groups "ibus-devel" group.
iBus project web page: http://code.google.com/p/ibus/
iBus dev group: http://groups.google.com/group/ibus-devel?hl=en
--- You received this message because you are subscribed to the Google Groups "ibus-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


回复