Mixing these 2 strategies for keyboard input will create unmanageable system. There are 2 strategies for the multi-language keyboard configuration. Multi-language keyboard configuration strategy Tray icon is available as kimpanel in plasma-widgets-addons package. Under those desktop environments, menu entry of their keyboard configuration utility or pop-up menu entry offered by clicking the associated tray icon may start ibus-setup for you.įor KDE, configuration of ibus is System_settings -> Hardware -> Input_devices/keyboard. For more complicated configuration such as swapping CapsLock and Ctrl, you need to install gnome-tweak and use it.įor non-GNOME system, the stand alone GUI configuration command ibus-setup can set up IM framework for ibus. The keyboard input needs to be configured from its GUI Settings -> Keyboard for basic configurations. (Please don't get confused by IM and XIM.)įor GNOME system (the default Debian Desktop environment), ibus package is automatically installed and activated. If the GUI system is Wayland, xwayland facilitates X connection for X applications. For X applications, the resulting keyboard data are passed to them through X connection with X Input method (XIM) protocol. For GTK and QT applications, the resulting keyboard data are passed to them through D-Bus communication. The installation of the input method (IM) framework package such as ibus (or fcitx5) together with associated packages enables to support all languages.įor the modern GUI system, keyboard inputs are processed by IM using IM engines. The simple keyboard input mechanism realized by the above configuration can't support some languages, such as Chinese and Japanese, properly. The resulting keyboard data are passed to the X applications through X connection with X Input method (XIM) protocol. The keyboard-configuration package take care their configuration.įor the X Window System, keyboard inputs are processed using X keyboard Extension (XKB). The Linux kernel and the X Window System process keyboard inputs independently. # udevadm trigger -subsystem-match=input -action=change To apply new settings, restarting the keyboard-setup service should suffice, otherwise you can try to restart kernel input system via udev:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |