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: Thu, 06 Jun 2019 17:38:16 +0200 [thread overview]
Message-ID: <87y32elo5z.fsf@gnu.org> (raw)
In-Reply-To: <87imtjt79n.fsf@roquette.mug.biscuolo.net> (Giovanni Biscuolo's message of "Thu, 06 Jun 2019 11:03:48 +0200")
Hi Giovanni,
Giovanni Biscuolo <g@xelera.eu> skribis:
> You are right, I overlooked that: I removed glibc-utf8-locales from my
> user profile, I just have glibc-locales now:
>
> ~$ ls -lah /var/guix/profiles/per-user/giovanni/guix-profile/lib/locale/2.28/ | grep en_US
> dr-xr-xr-x 3 root root 4.0K Jan 1 1970 en_US
> dr-xr-xr-x 3 root root 4.0K Jan 1 1970 en_US.UTF-8
D’oh!
> In fact make-glibc-locales in base.scm "just" installs all locales in
> "not normalized codeset" with:
>
> [...]
> (replace 'build
> (lambda _
> (invoke "make" "localedata/install-locales"
> "-j" (number->string (parallel-job-count)))))
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.
The “normalized codeset” is described in the libc manual (info "(libc)
Using gettextized software") and (info "(libc) Locale Names").
Anyway, I’ve posted patches to refactor things a bit and to create those
symlinks in ‘glibc-locales’:
https://issues.guix.gnu.org/issue/36116
Let me know what you think.
Thanks!
Ludo’.
next prev parent reply other threads:[~2019-06-06 15:39 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 [this message]
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
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=87y32elo5z.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).