unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 40273@debbugs.gnu.org
Subject: bug#40273: installer: No way to input Latin characters with non-Latin keyboard layouts
Date: Fri, 3 Apr 2020 02:38:16 +0200	[thread overview]
Message-ID: <20200403003816.oywdf75mj7yjzygj@pelzflorian.localdomain> (raw)
In-Reply-To: <87k12yql0i.fsf@gnu.org>

On Thu, Apr 02, 2020 at 11:45:01AM +0200, Ludovic Courtès wrote:
> The attached patch fixes that.  I’ve confirmed that it works as intended
> in Xorg and in the console

Thank you, it works fine, even for entering the LUKS passphrase after
GRUB in the Linux kernel.  Only GRUB uses U.S. QWERTY layout.

> (I’m not sure it works in GDM, but it
> definitely works in an xterm in ratpoison, for instance.)

GDM retains my U.S. English layout even after herd stop xorg-server
and deleting all files in /var/lib/gdm.  Deleting all files also made
my fonts different in gnome-terminal, Icecat, Emacs, also
gnome-initial-setup got run again, but these issues are unrelated to
this bug and do not happen if one does not “sudo rm -rf
/var/lib/gdm/.*”.



> I was wondering whether to push the patch as-is or to require people to
> write:
> 
>   (keyboard-layout '("ar" "fr") …)
> 
> instead.  Maybe it’s OK to leave the comma here.

Lists seem more consistent with the Scheme syntax.


> 
> However, I noticed that this doesn’t work in GRUB.  Actually, even
> (keyboard-layout "fr") doesn’t work in GRUB (at the command line after
> the boot menu), which seems like a regression.

I suppose on GRUB using at_keyboard it worked in the past?

For me there’s no regression because keyboard layouts never worked
(using usb keyboard rather than at keyboard), see
<https://issues.guix.info/issue/35585#9>.

Back then I was told to open a bug at GRUB, which I have not done.
There are other old bugs on keyboard layouts and bugs on USB keyboards
among the GRUB bugs at Savannah though.  I find an e-mail to bug-grub
concerning the same issue
<https://lists.gnu.org/archive/html/bug-grub/2017-10/msg00003.html>,
but no bug at Savannah.  I will not open a bug I suppose, also the
GRUB manual says many keymaps don’t work well.

https://www.gnu.org/software/grub/manual/grub/html_node/Internationalisation.html#Input-terminal

It says “Own keyboard implementations (at_keyboard and usb_keyboard)
supports any key but work on one-char-per-keystroke. So no dead keys
or advanced input method. Also there is no keymap change hotkey. In
practice it makes difficult to enter any text using non-Latin
alphabet. Moreover all current input consumers are limited to ASCII.”


f5961dd5854cec1ed9a41365836d63aa15256642 for usb keyboard was a bad
commit (passphrase input was QWERTY, back then usb keyboard did not
work at all in GRUB menu).

Regards,
Florian

  reply	other threads:[~2020-04-03  0:39 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) [this message]
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)
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=20200403003816.oywdf75mj7yjzygj@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=40273@debbugs.gnu.org \
    --cc=ludo@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).