From: "Wismill" <[email protected]>
To: [email protected]
Subject: [ANNOUNCE] libxkbcommon 1.13.0
Date: Wed, 05 Nov 2025 09:43:02 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
Dear all,
I am pleased to announce the release of libxkbcommon 1.13.0:
https://github.com/xkbcommon/libxkbcommon/tree/xkbcommon-1.13.0
Our documentation (lib + XKB format) is available as usual at:
https://xkbcommon.org/doc/current/
Changelog
---------
The highlight of this release is the introduction of the XKB **extensions directories**,
a new mechanism to facilitate keyboard layout packaging and distribution.
See https://xkbcommon.org/doc/current/packaging-keyboard-layouts.html for further details.
## API
### Breaking changes
- context: The default include paths initialization is *delayed* until required.
This is more efficient for clients that only get the keymap from the server and
thus do not need to look up any XKB files.
It also fixes the issue of containerized apps that lack access to XKB directories.
This is marked as a breaking change, because changing environment variables
relevant to include paths between the call to `xkb_context_new()` and any
function requiring the default path initialization — e.g.
`xkb_keymap_new_from_names()` — will have a different behavior than previous
xkbcommon versions. However this situation is deemed unlikely.
### New
- Added keysyms from latest [xorgproto]
\(commit: `f973f7db89571f61e96cb0a55f416d3e67a75663`, [xorproto-102]):
- `XKB_KEY_XF86MediaPlayPause`
- `XKB_KEY_XF86Exit`
- `XKB_KEY_XF86AudioBassBoost`
[xorproto-102]: https://gitlab.freedesktop.org/xorg/proto/xorgproto/-/merge_requests/102
- Added the XKB **extensions directories**, a new mechanism to facilitate
keyboard layout packaging and distribution.
- rules: Added lightweight composition of rules files: for a given ruleset `<ruleset>`,
the *optional* files `<ruleset>.pre` and `<ruleset>.post` of each include
path are respectively *prepended* and *appended* to the main rules file.
The resulting rule set is equivalent to:
```
! include <include path 1>/rules/<ruleset>.pre // only if defined
…
! include <include path n>/rules/<ruleset>.pre // only if defined
! include <ruleset> // main rules file
! include <include path 1>/rules/<ruleset>.post // only if defined
…
! include <include path n>/rules/<ruleset>.post // only if defined
```
## Tools
### Fixes
- `xkbcli how-to-type`: Fixed Compose lookup when the entry keysym is not canonical.
Git tag:
--------
git tag: xkbcommon-1.13.0
git commit: 3049d310694fd70f1269bf48a1200aa4259e79b1
Cheers, Pierre Le Marre (aka Wismill)
reply other threads:[~2025-11-05 9:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f60e22d2bc261ab9c0ad11c81e15689fe9641951@wismill.eu \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox