Vboard and system layout

[alioth9]

As I understand Vboard/uinput it send raw keycodes just like it would be by a physical keyboard. So it is affected by system (Xkb) choice of layout. But the default label on vboard assume a us qwerty layout. For example assuming a de(qwertz) layout is enabled, the Y and Z beeing switch by the layout, taping Y on vboard will produce a z. It will cause some confusion, it would be interesting to document that behaviour.

It could be possible to provide some variant of vboard.py like vboard_qwertz.py with adapted labels. It could be provided as per demand (a few).

[mdev588]

Good catch I never used other than us layout. I will add a note on docs and your suggestion is good.

[alioth9]

Obvioously the problem is that for each modification, every vboard variant had to be modified too.

It could be good also to mention that vboard follow Xkb layout: not only concerning compatibility and label but also because it is a feature, it means that you can switch language as per xkb (label don't follow though) and more importantly we can use AltGr (RIght Alt) layer, like on a regular physical keyboard (as it is emulated), for special characters and diacritics.

[AlexP11223]

it send raw keycodes just like it would be by a physical keyboard. So it is affected by system (Xkb) choice of layout.

iirc the Florence keyboard uses this approach. It somehow handles layout switching automatically (without hardcoded labels for each language).

Peek.2025-03-01.21-16.mp4