From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Locale of build environments
Date: Sat, 14 Feb 2015 19:12:13 -0500 [thread overview]
Message-ID: <87a90gghia.fsf@netris.org> (raw)
In-Reply-To: <87mw4iq3uz.fsf_-_@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\?\= \=\?utf-8\?Q\?\=22's\?\= message of "Thu, 12 Feb 2015 21:20:04 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver <mhw@netris.org> skribis:
>
>> Guile converts POSIX byte strings (e.g. file names) to strings using to
>> the current locale encoding, but the default locale in our build
>> environment is "C" which means ASCII-only.
>>
>> I would advocate using a UTF-8 locale for all builds by default.
>
> Note that this was already the case before locales were moved out of the
> ‘glibc’ package. Also, the early bootstrap environment (until
> ‘glibc-final’ is used) doesn’t have locales.
>
> For the non-bootstrap environment, we could make a ‘glibc-utf8-locale’
> that would only include ‘en_US.UTF-8’ (or a few more, but which one?)
> and add it to the implicit inputs of ‘gnu-build-system’.
>
> WDYT?
Sounds good to me!
Thanks,
Mark
next prev parent reply other threads:[~2015-02-15 0:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 20:14 CA certificates Andreas Enge
2015-02-12 16:44 ` Andreas Enge
2015-02-12 17:26 ` Mark H Weaver
2015-02-12 19:48 ` Andreas Enge
2015-02-12 20:20 ` Locale of build environments Ludovic Courtès
2015-02-12 20:28 ` Andreas Enge
2015-02-15 0:12 ` Mark H Weaver [this message]
2015-02-26 23:16 ` Ludovic Courtès
2015-02-26 23:45 ` Mark H Weaver
2015-02-27 10:36 ` Ludovic Courtès
2015-02-27 14:13 ` Ludovic Courtès
2015-03-01 16:48 ` Ludovic Courtès
2015-02-13 7:28 ` CA certificates Mark H Weaver
2015-02-13 10:23 ` Andreas Enge
2015-02-12 20:30 ` 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=87a90gghia.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@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).