-
Notifications
You must be signed in to change notification settings - Fork 124
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Compose: allow overlapping sequences
Currently xkbcommon does not support Compose overlapping sequences, unlike GTK and ibus. It means a sequence that is a prefix to a longer one is simply discarded with a warning. This is unfortunate: - There is discrepency for users of xkbcommon, e.g. Qt-based apps. - It is impossible to have a sequence that is the prefix of another one. As a consequence, if one imports e.g. the system locale Compose file (as many – most ? – custom Compose files do), some sequences become impossible. Example: I used `<Multi_key> <minus> <period> : "•" U2022` but upstream change in libX11 added `<Multi_key> <minus> <period> <e> : "ė̄"`, so I had to introduce an alternative sequence for Qt apps, although the previous one works in GTK-based apps. This commit introduces the new following API: - Macro `XKB_COMPOSE_HAS_OVERLAPPING_SEQUENCES_SUPPORT` to test overlapping sequences support at compile time via `#ifdef`. - `xkb_compose_compile_flags`: `XKB_COMPOSE_COMPILE_OVERLAPPING_SEQUENCES`: Allow overlapping sequences - `xkb_compose_status`: - `XKB_COMPOSE_CANDIDATE`: A complete sequence has been matched, but a longer sequence also exists. - `XKB_COMPOSE_CANDIDATE_ACCEPTED`: The last sequence was accepted due to an unmatched keysym.
- Loading branch information
Showing
13 changed files
with
423 additions
and
97 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.