From: Alexey Gladkov <gladkov.alexey@gmail.com>
To: Linux console tools development discussion <kbd@lists.altlinux.org>
Subject: [kbd] I: kbd + xkb
Date: Mon, 14 Feb 2022 13:49:18 +0100 [thread overview]
Message-ID: <20220214124918.r7vjp7epspvw35jd@example.org> (raw)
Hi!
I implemented initial proof of concept[1] for using layouts from XKB.
Using xkbcommon I process loadkeys arguments and convert the resulting
configuration into a kernel keymap. Only what is supported by the kernel
is converted.
This support does not replace regular keymaps. There are no plans for
this.
The command looks like:
loadkeys --xkb-layout="us,ru,fr" --xkb-options="grp:caps_toggle"
This implementation is inspired by the console-setup[2] project. Many
thanks to Anton Zinoviev for help.
At the moment compose is not implemented. This is because xkbcommon does
not provide an API for iterating over a compose table. I hope to solve
this problem in the future.
If you're interested then comments, bug reports and patches are welcome!
[1] https://github.com/legionus/kbd/tree/xkbcommon
[2] https://salsa.debian.org/installer-team/console-setup.git
--
Rgrds, legion
reply other threads:[~2022-02-14 12:49 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=20220214124918.r7vjp7epspvw35jd@example.org \
--to=gladkov.alexey@gmail.com \
--cc=kbd@lists.altlinux.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).