From: Mathieu Othacehe <m.othacehe@gmail.com>
To: 40273@debbugs.gnu.org
Subject: bug#40273: installer: No way to input Latin characters with non-Latin keyboard layouts
Date: Sun, 29 Mar 2020 19:53:48 +0200 [thread overview]
Message-ID: <878sjjt5cj.fsf@gmail.com> (raw)
In-Reply-To: <20200329171609.puseiw4d4b6cxgd7@pelzflorian.localdomain>
Hey,
> I test the Newt-based Debian 10 installer via QEMU. When I select
> English language with Arabic keymap, I can choose a key combination
> for switching the layout, Alt+Shift by default. But I cannot choose
> between AZERTY and QWERTY, I always get QWERTY.
Defining such a combination could be an option too. I tried to implement
the mechanism I proposed, but had multiple problems:
* Shepherd is using /dev/console as an output and some messages are
polluting the help line displayed at the bottom of the screen. I'm not
sure how to solve it.
Shepherd could poll /dev/log so that once syslog is available it stops
using /dev/console.
* Guile-newt functions "newt-set-help-callback" and
"add-component-callback" seem to be tripping over each other and I'm
having a hard time trying to understand why.
Regardless of this keyboard layout issue, having a help menu for the
installer could be useful to display the shortcuts for instance.
Thanks,
Mathieu
next prev parent reply other threads:[~2020-03-29 17:54 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 [this message]
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)
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=878sjjt5cj.fsf@gmail.com \
--to=m.othacehe@gmail.com \
--cc=40273@debbugs.gnu.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.
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).