removal of the VKEY_NEXT binding which is a duplicate
in Xkb, XKB_KEY_KP_Next has the same value as XKB_KEY_KP_Page_Down
the KP versions of Home/End/PgUp/PdDn are only translated when the shift modifier is down;
this prevents intercepting the key in case we should have a character.
the Xkb state is initialized according to that of the Xserver, which lets Xkb know about NumLock
always extract the utf32 character by stateful translation, which numpad also requires
xkbcommon notes about xkb_keysym_to_utf32:
This function does not perform any keysym-transformations.
Therefore, prefer to use xkb_state_key_get_utf32() if possible.
This fixes the keypad entry on X11.
The changes are as follows:
VKEY_NEXTbinding which is a duplicate in Xkb,XKB_KEY_KP_Nexthas the same value asXKB_KEY_KP_Page_Downxkb_keysym_to_utf32: