Contents
What kind of format does Wayland use for keyboard?
At the protocol level, wayland has a wl_keyboard.keymap event. This event contains a file descriptor to the keymap and a format classifier. Right now, only one format is defined: “xkb”.
Which is the next input device on Wayland?
The next input device on our list is keyboards, but we need to stop and give you some additional context before we discuss them. Keymaps are an essential detail involved in keyboard input, and XKB is the recommended way of handling them on Wayland.
How are input groups used in the Wayland protocol?
Input groups are used to switch between various keyboard layouts, such as toggling between ISO and ANSI layouts, or for more language-specific features. The interpretation of modifiers is keymap-specific. You should forward them both to XKB to deal with.
Which is the common code from XKB ( X keyboard )?
To solve this problem, we use a library called “xkbcommon”, which is named for its role as the common code from XKB (X KeyBoard) extracted into a standalone library. XKB defines a huge number of key symbols, such as XKB_KEY_A, and XKB_KEY_ssharp (ß, from German), and XKB_KEY_kana_WO (を, from Japanese).
Can you change the keyboard layout in sway?
Eventually, sway will add the ability to change layouts during runtime. This pull request adds swaymsg input subcommands to set XKB options at runtime; it’s presently in the development branch ( wlroots ). If it is released as in that PR, you’d be able to issue commands like these to change the keyboard:
Are there any Wayland compositors that talk to sway?
Wayland does not provide a server like X, so each Wayland compositor has to implement its own method for setting or changing layouts — generic tools like setxkbmap are out unless/until a protocol is defined/adopted that will allow the tool to talk to any compositor. Eventually, sway will add the ability to change layouts during runtime.