- Package:
- console-setup
- Source:
- console-setup
- Submitter:
- Holger Wansing
- Date:
- 2020-12-07 21:45:05 UTC
- Severity:
- normal
Hi, we are currently in the process of adding Kabyle as a new language to our debian-installer. The locale settings for the Kabyle language are supposed to be language: Kabyle - kab country: Algeria - DZ -> kab_DZ I have added Kabyle to the localechooser package, and it correctly shows up as a language in the "Choose language" dialog. But I have a problem now in the text-based installer: (in graphical installer everything is ok!) While displaying the installer dialogs in Kabyle is fine, it fails to switch the keyboard to the desired "Berber (Latin)" layout. I also noticed that the installer states to use "kab_DZ" as locale, while in the other languages there is an UTF-8 locale (like "de_DE.UTF-8" for German). Maybe that's the reason for the installer failing to switch keyboard correctly ... ? When diagnosing the list of supported locales, I see that in locales package the situation is the same: ned@t520:~$ grep kab /usr/share/i18n/SUPPORTED kab_DZ UTF-8 ned@t520:~$ Only "kab_DZ" shows up in /usr/share/i18n/SUPPORTED, instead of "kab_DZ.UTF-8/UTF-8" like for many other languages. Please accept my appologies, if I got something wrong here, but for me it seems there is something wrong/missing... ? Shouldn't UTF-8 be the default for years already? (Hmm, not for all languages/locales maybe ... ?) Stay save Holger
Hi, I confirm that the kab_DZ is available in glibc, it has been added in version 2.27. You can also check that the date is properly displayed on a running Debian system. $ LC_ALL=kab_DZ date Sed 31 Tub 2020 17:36:48 CET Keyboard layout is not something handled by the glibc locales. This is correct, because the kab_DZ locale is only available as UTF-8. de_DE.UTF-8 exists because the default de_DE locale is ISO-8859-1 encoded. The same way there is also a de_DE@euro locale defaulting to ISO-8859-15. This is perfectly normal. There are many other locales without UTF-8 in their name, see for example fy_DE or en_NG. Yes, that's exactly because UTF-8 is the default for years already that the Kabylian locale is only available as kab_DZ. Regards, Aurelien
Aurelien Jarno <aurelien@aurel32.net> wrote:
Ok, thanks for taking the time to confirm, that this seems no issue related
to locales/glibc !
With the above explanation it makes sense so far :-)
So, sorry for the noise.
Which brings me to the next point in the list of packages that might cause
this, and that being console-setup.
Re-assigning and re-titling accordingly.
@Anton: maybe you could take a look, why switching keyboard to dz(la) does
not work?
I am on the way of adding a new language ("Kabyle") to the installer, and
switching the keyboard layout now fails.
Looking at the other languages/keymaps, and given that the Kabyle translator
proposed "Berber Latin" as keyboard layout, and Algeria (DZ) being the default
country for that language, I came to the assumption, that
XKBLAYOUT=dz # Algeria
XKBVARIANT=la # Berber (Latin)
might be correct (see
https://salsa.debian.org/installer-team/console-setup/-/commit/2da68d8e64aac78306e864aea0ea0ea967cf51af )
But unfortunately it does not work.
Setting the above values in /etc/default/keyboard and then executing "/bin/setupcon"
simply does nothing, the keyboard stays unchanged (trying in the text installer!
when using the graphical installer, the keyboard seems to switch correctly, but
then there are other problems.)
Many thanks!
Holger
Hi, I have just seen you patch to localechooser: https://salsa.debian.org/installer-team/localechooser/-/commit/e7c432b8e7579511ff24ca554940b23cd0a9d482#97d66a6f96fa0a78b8cc86e86b52a0144da74883_54_53 I think the locale entry is wrong, as discussed above, it should be kab_DZ instead of kab_DZ.UTF-8. Just like then entries around are ks_IN or km_KH. Regards, Aurelien
[ Forgot to sent to debian-boot as well, so resending ]
Aurelien Jarno <aurelien@aurel32.net> wrote:
Ok, thanks for taking the time to confirm, that this seems no issue related
to locales/glibc !
With the above explanation it makes sense so far :-)
So, sorry for the noise.
Which brings me to the next point in the list of packages that might cause
this, and that being console-setup.
Re-assigning and re-titling accordingly.
@Anton: maybe you could take a look, why switching keyboard to dz(la) does
not work?
I am on the way of adding a new language ("Kabyle") to the installer, and
switching the keyboard layout now fails.
Looking at the other languages/keymaps, and given that the Kabyle translator
proposed "Berber Latin" as keyboard layout, and Algeria (DZ) being the default
country for that language, I came to the assumption, that
XKBLAYOUT=dz # Algeria
XKBVARIANT=la # Berber (Latin)
might be correct (see
https://salsa.debian.org/installer-team/console-setup/-/commit/2da68d8e64aac78306e864aea0ea0ea967cf51af )
But unfortunately it does not work.
Setting the above values in /etc/default/keyboard and then executing "/bin/setupcon"
simply does nothing, the keyboard stays unchanged (trying in the text installer!
when using the graphical installer, the keyboard seems to switch correctly, but
then there are other problems.)
Many thanks!
Holger
Hi, Aurelien Jarno <aurelien@aurel32.net> wrote: Ah, ok. Thanks for the pointer, I will give that a try. Holger
Hi, Holger Wansing <hwansing@mailbox.org> wrote: That does not change anything, sadly. I would change that anyway (later), to make it at least consistent. Holger
Hi, Holger Wansing <hwansing@mailbox.org> wrote: generated file (which then should be used by loadkeys) only contains keymaps 0-4,6,8,10,12,14 strings as usual However, I suppose it should contain several "keycode x = <code> <code> <code>" lines, right? The complete call for dz(la) is: "usr/bin/ckbcomp -backspace del -model pc105 dz la >$TMPFILE" Executing this on a Debian buster system, gives a lot of output with above mentioned "keycode x = ..." lines. So I guess that is ok. (Setting keymap to dz(la) with setupcon on such buster system works fine BTW!) Diagnosting where is the difference between a running Debian stable system and the d-i environment shows, that in the d-i 'ckbcomp' is a symlink to ckbcomp-mini. So, I wonder what's the difference between ckbcomp and -mini? Any ideas, why the latter fails? Holger
Hi, Holger Wansing <hwansing@mailbox.org> wrote: I changed that now in git. And I also disabled Kabyle language in the text-based installer for now, so if someone wants to do some testing regarding this keyboard switching problem, he needs to use the bullseye alpha3 images for that, if Kabyle is no longer available in the daily's. Holger