From: "Ludovic Courtès" <ludo@gnu.org>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: 36076@debbugs.gnu.org
Subject: bug#36076: Manual should clarify that glibc-utf8-locales is needed by default on foreign distros
Date: Wed, 12 Jun 2019 16:40:05 +0200 [thread overview]
Message-ID: <875zpavpdm.fsf@gnu.org> (raw)
In-Reply-To: <87imtcp47p.fsf@roquette.mug.biscuolo.net> (Giovanni Biscuolo's message of "Tue, 11 Jun 2019 16:49:14 +0200")
Hello Giovanni,
Giovanni Biscuolo <g@xelera.eu> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
> [...]
>
>> We should fix it, notably because libc automatically falls back to the
>> normalized codeset (that is, if you choose “en_US.uTF--8”, it eventually
>> tries to read data for “en_US.utf8”.) I wonder why the
>> ‘install-locales’ rule doesn’t to it.
>
> Me too: do you think it's appropriate to report this upstream?
> I can manage this if needed, of course.
It would be great, yes!
>> The “normalized codeset” is described in the libc manual (info "(libc)
>> Using gettextized software") and (info "(libc) Locale Names").
>
> Herm... I'm still too web dependent, I have to correctly install all
> infos :-O
Just type these ‘info’ commands and it should Just Work on Guix System.
:-)
> Reading your refactored build-locale in (gnu build locale), as used
> e.g. in (gnu system locale), makes me wonder if Guix could allow users to
> define their preferred locales in a (operating-system ...) declaration,
> having "guix system" building only the needed ones... but that's another
> story
That’s already the case.
It would be nice to have it for Guix on foreign distros, as discussed in
the “Parameterized packages” thread.
Thanks,
Ludo’.
prev parent reply other threads:[~2019-06-12 14:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 18:39 bug#36076: Manual should clarify that glibc-utf8-locales is needed by default on foreign distros Jack Hill
2019-06-05 13:17 ` Ludovic Courtès
2019-06-06 4:46 ` Jack Hill
2019-06-06 7:57 ` Ludovic Courtès
2019-06-05 17:28 ` Giovanni Biscuolo
2019-06-06 4:32 ` Jack Hill
2019-06-06 9:03 ` Giovanni Biscuolo
2019-06-06 15:38 ` Ludovic Courtès
2019-06-06 16:56 ` Jack Hill
2019-06-07 21:12 ` Ludovic Courtès
2019-06-07 22:59 ` Jack Hill
2019-06-11 14:49 ` Giovanni Biscuolo
2019-06-12 14:40 ` Ludovic Courtès [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
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=875zpavpdm.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=36076@debbugs.gnu.org \
--cc=g@xelera.eu \
/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).