From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Locale
Date: Tue, 13 Oct 2015 13:55:38 +0200 [thread overview]
Message-ID: <idjtwpvyocl.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <20151013113842.GA4687@debian>
Hi Andreas,
> although I am afraid to raise allergic reactions, I must say that locales
> do not seem to work any more on my guix on debian setting since the last
> upgrade... Although I chose a utf8 locale, I am not seeing special characters
> in mutt (taken from guix).
>
> Hopefully it is just a simple matter of setting things up.
> Currently I have this:
> export LOCPATH=$HOME/.guix-profile/lib/locale:$HOME/.guix-profile/share/locale
> as was suggested at some point in time by the search path directives.
> Do I need to add "2.22/" to them?
according to the manual section “Locales” Guix’s libc respects
GUIX_LOCPATH.
libc suffixes each entry of @code{GUIX_LOCPATH} with @code{/X.Y}, where
@code{X.Y} is the libc version---e.g., @code{2.22}. This means that,
should your Guix profile contain a mixture of programs linked against
different libc version, each libc version will only try to load locale
data in the right format.
When using Guix on top of another distribution you should only set
GUIX_LOCPATH to make sure that only Guix programmes use the locales in
your profile. All other applications (those of the host system) will
continue to use the host system locales.
Hope this helps!
~~ Ricardo
next prev parent reply other threads:[~2015-10-13 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 11:38 Locale Andreas Enge
2015-10-13 11:55 ` Ricardo Wurmus [this message]
2015-10-13 13:05 ` Locale Daniel Pimentel
2015-10-14 19:47 ` Locale Andreas Enge
2015-10-14 21:45 ` Locale Ludovic Courtès
2015-10-13 19:21 ` Locale Efraim Flashner
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=idjtwpvyocl.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=andreas@enge.fr \
--cc=guix-devel@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 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.