> This is possible in Wayland, it's up to the compositor. Typically compositor uses libxkbcommon which suffers from the same problems that X server had. > Rem

> This is possible in Wayland, it's up to the compositor. Typically compositor uses libxkbcommon which suffers from the same problems that X server had. > Remote keyboards are just like physical keyboards. Just configure VNC's keyboard to use the correct layout. It is inconvenient and I don't think it would work. There is no such thing as "VNC keyboard". VNC client sends keysyms over the wire, so the VNC server has to convert them back to a key number, switch to necessary layout if there are several of them, turn off modifiers like Shift if necessary. This is too complicated. For example, x11vnc server doesn't support non-latin input correctly. > (BTW I'm not sure I understand what you mean by "Everything is broken") That many VNC servers cannot handle non-latin input correctly. > however in Wayland on-screen keyboards _can_ send unicode to the compositor via the standard text-input protocol This looks like an extension for implementing IME. You can see that there is no key press or key release events. These events are defined in wayland protocol spec [1] and they still use a key number. So you cannot send key press/release events for characters not present in current keyboard layout. [1] https://wayland.freedesktop.org/docs/html/apa.html#protocol-spec-wl_keyboard https://wayland.freedesktop.org/docs/html/apa.html#protocol-...