From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Bengt Richter <bokr@bokr.com>
Cc: 40273@debbugs.gnu.org
Subject: bug#40273: installer: No way to input Latin characters with non-Latin keyboard layouts
Date: Sat, 4 Apr 2020 01:17:50 +0200 [thread overview]
Message-ID: <20200403231750.ddmqx6ekr35eye2u@pelzflorian.localdomain> (raw)
In-Reply-To: <20200402232743.GA2810@LionPure>
On Fri, Apr 03, 2020 at 01:27:43AM +0200, Bengt Richter wrote:
> I think I saw that PureOS was able to handle
> different-layout keyboards in different concurrent sessions -- different keyboards and displays
> can be attached to different "seats" -- or something like that, I obviously don't know much yet ;-)
>
> Anyway, to the point: even if I'm wrong about PureOS handling concurrent
> different-layout keyboards, I think that would be a good goal
> for GuixOS/Hurd/Shepherd to implement.
From what I understand from
<https://github.com/xkbcommon/libxkbcommon/blob/master/doc/quick-guide.md>,
there can be per-device keyboard layouts, but they are not handled by
XKB options. If a device specifier were added to the keyboard-layout
constructor, the device specifier would need to be turned into
appropriate xorg.conf MatchUSBID or similar.
Regards,
Florian
next prev parent reply other threads:[~2020-04-03 23:18 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 13:42 bug#40273: installer: No way to input Latin characters with non-Latin keyboard layouts pelzflorian (Florian Pelz)
2020-03-28 19:45 ` Mathieu Othacehe
2020-03-30 10:44 ` pelzflorian (Florian Pelz)
2020-03-30 11:35 ` Mathieu Othacehe
2020-03-30 17:11 ` pelzflorian (Florian Pelz)
2020-03-30 17:31 ` pelzflorian (Florian Pelz)
2020-03-31 15:35 ` Ludovic Courtès
2020-03-31 16:55 ` pelzflorian (Florian Pelz)
2020-04-01 20:33 ` Bengt Richter
2020-04-02 6:24 ` pelzflorian (Florian Pelz)
2020-04-02 9:45 ` Ludovic Courtès
2020-04-03 0:38 ` pelzflorian (Florian Pelz)
2020-04-03 1:11 ` pelzflorian (Florian Pelz)
2020-04-03 13:31 ` pelzflorian (Florian Pelz)
2020-04-03 13:59 ` pelzflorian (Florian Pelz)
2020-04-03 15:20 ` Ludovic Courtès
2020-04-03 15:56 ` pelzflorian (Florian Pelz)
2020-04-05 14:03 ` Ludovic Courtès
2020-04-05 20:02 ` pelzflorian (Florian Pelz)
2020-04-05 21:26 ` Ludovic Courtès
2020-03-29 15:04 ` Ludovic Courtès
2020-03-29 17:16 ` pelzflorian (Florian Pelz)
2020-03-29 17:53 ` Mathieu Othacehe
2020-03-30 10:39 ` Mathieu Othacehe
2020-03-30 12:39 ` pelzflorian (Florian Pelz)
2020-03-31 15:29 ` Ludovic Courtès
2020-04-01 12:49 ` Mathieu Othacehe
2020-03-31 15:28 ` Ludovic Courtès
2020-04-01 12:52 ` Mathieu Othacehe
2020-04-02 10:25 ` Ludovic Courtès
2020-04-02 11:40 ` Mathieu Othacehe
2020-04-06 7:52 ` Ludovic Courtès
2020-04-06 13:14 ` Mathieu Othacehe
2020-04-07 9:49 ` Ludovic Courtès
2020-04-07 17:14 ` Mathieu Othacehe
2020-04-02 23:27 ` Bengt Richter
2020-04-03 23:17 ` pelzflorian (Florian Pelz) [this message]
2020-04-08 7:20 ` Bengt Richter
2020-04-08 9:42 ` Ludovic Courtès
2020-04-08 21:11 ` Bengt Richter
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200403231750.ddmqx6ekr35eye2u@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=40273@debbugs.gnu.org \
--cc=bokr@bokr.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).