From: Andy Wingo <wingo@pobox.com>
To: Zefram <zefram@fysh.org>
Cc: 22902-done@debbugs.gnu.org
Subject: bug#22902: GUILE_INSTALL_LOCALE not equivalent to setlocale
Date: Sun, 07 Aug 2016 23:53:04 +0200 [thread overview]
Message-ID: <87d1lknt4v.fsf@pobox.com> (raw)
In-Reply-To: <20160304033452.GB1318@fysh.org> (zefram@fysh.org's message of "Fri, 4 Mar 2016 03:34:52 +0000")
On Fri 04 Mar 2016 04:34, Zefram <zefram@fysh.org> 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.
I believe this is fixed in both 2.0 and master. Thanks for the report.
Andy
prev parent reply other threads:[~2016-08-07 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 3:34 bug#22902: GUILE_INSTALL_LOCALE not equivalent to setlocale Zefram
2016-06-20 16:16 ` Andy Wingo
2016-08-07 21:53 ` Andy Wingo [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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1lknt4v.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=22902-done@debbugs.gnu.org \
--cc=zefram@fysh.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.
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).