From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 40534-done@debbugs.gnu.org
Subject: bug#40534: Installer: List of languages should be focused on translated ones
Date: Sun, 19 Apr 2020 01:27:48 +0200 [thread overview]
Message-ID: <20200419012748.45ab01dc@alma-ubu> (raw)
In-Reply-To: <20200410134644.osijdq7aoymacak5@pelzflorian.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
On Fri, 10 Apr 2020 15:46:44 +0200
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> wrote:
> On Fri, Apr 10, 2020 at 01:34:40PM +0200, Björn Höfling wrote:
> > When starting the Guix installer, the first question is to choose a
> > language.
> >
> > You are confronted with a very long list of all sorts of languages.
> > When you then choose one of the untranslated ones, you just get
> > back to English.
> >
> > Wouldn't it be better to just show those where really (some)
> > translations are available?
>
> The chosen language should affect the locale in the generated
> config.scm, does it not? If the locale in config.scm is correct, then
> even if Guix has no translation at least the installed system will
> have translations e.g. for GNOME and I believe this issue can be
> closed. Just the installer messages remain untranslated English for
> now.
You are right, that's a good argument at the end of installation.
Closing this one, and waiting for Guix-world-domination with full
translations in all available languages :-)
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2020-04-18 23:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 11:34 bug#40534: Installer: List of languages should be focused on translated ones Björn Höfling
2020-04-10 13:46 ` pelzflorian (Florian Pelz)
2020-04-18 23:27 ` Björn Höfling [this message]
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=20200419012748.45ab01dc@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=40534-done@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.