From: Peter Brett <peter@peter-b.co.uk>
To: guile-devel@gnu.org
Subject: Re: Accessing the environment's locale encoding settings
Date: Wed, 16 Nov 2011 16:32:06 +0000 [thread overview]
Message-ID: <we1mhb2458qh.fsf@ssclt001.ee.surrey.ac.uk> (raw)
In-Reply-To: CA+U71=Py2yLi5FB1bhPPHw5bFkpUpTCbosLKGefTnSKy4Wds6g@mail.gmail.com
Noah Lavine <noah.b.lavine@gmail.com> writes:
> It seems like the right thing to do might be to do setlocale(LC_ALL,
> "") in Guile's main(). Let me argue that this accomplishes two goals
> which we want to accomplish
That seems entirely reasonable to me, as long as libguile users can
still set a non-environment locale before first entering Guile mode and
have libguile respect that.
However, I'd still be concerned about the case where filenames are
passed on the command line in an encoding that differs from the
environment encoding. A few months ago, Mark mentioned that he was
looking at "safe" encodings for filenames. I wonder if that's relevant
to command-line argument processing?
Peter
--
Peter Brett <peter@peter-b.co.uk>
Remote Sensing Research Group
Surrey Space Centre
next prev parent reply other threads:[~2011-11-16 16:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 0:13 Accessing the environment's locale encoding settings Ludovic Courtès
2011-11-16 2:00 ` Bruno Haible
2011-11-16 10:35 ` Ludovic Courtès
2011-11-16 16:11 ` Noah Lavine
2011-11-16 16:32 ` Peter Brett [this message]
2011-11-18 22:17 ` Mark H Weaver
2011-11-20 16:55 ` Bruno Haible
2011-11-20 17:41 ` Ludovic Courtès
2011-11-20 19:44 ` Mike Gran
2011-11-23 23:28 ` Ludovic Courtès
2011-11-24 4:42 ` Mike Gran
2011-11-24 13:16 ` Peter Brett
2011-11-25 2:11 ` Mark H Weaver
2011-12-15 19:08 ` Ludovic Courtès
2011-11-20 20:12 ` Bruno Haible
2011-12-15 0:41 ` 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://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=we1mhb2458qh.fsf@ssclt001.ee.surrey.ac.uk \
--to=peter@peter-b.co.uk \
--cc=guile-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.
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).