[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#22902: GUILE_INSTALL_LOCALE not equivalent to setlocale
From: |
Andy Wingo |
Subject: |
bug#22902: GUILE_INSTALL_LOCALE not equivalent to setlocale |
Date: |
Mon, 20 Jun 2016 18:16:46 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
On Fri 04 Mar 2016 04:34, Zefram <address@hidden> writes:
> The documentation claims that setting GUILE_INSTALL_LOCALE=1 in the
> environment is equivalent to calling (setlocale LC_ALL "") at startup.
> Actually there is at least one difference: calling setlocale causes ports
> (both primordial and later-opened) to be initially configured for the
> locale's nominal character encoding, but setting the environment variable
> does not. Setting the environment variable leaves the port encoding at
> #f, functioning as ISO-8859-1, just as if locale had not been invoked
> at all. I do see some effects from setting the environment variable,
> specifically message strings affecting strftime.
Indeed! Thank you for this analysis; I was wondering why I was getting
terrible backtraces in Guile master.
Andy
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#22902: GUILE_INSTALL_LOCALE not equivalent to setlocale,
Andy Wingo <=