From: Andy Wingo <wingo@pobox.com>
To: Zefram <zefram@fysh.org>
Cc: 20822@debbugs.gnu.org, ludo@gnu.org
Subject: bug#20822: environment mangled by locale
Date: Fri, 24 Jun 2016 07:57:43 +0200 [thread overview]
Message-ID: <87eg7njfhk.fsf@pobox.com> (raw)
In-Reply-To: <20150616041736.GA2718@fysh.org> (zefram@fysh.org's message of "Tue, 16 Jun 2015 05:17:36 +0100")
On Tue 16 Jun 2015 06:17, Zefram <zefram@fysh.org> writes:
> When guile-2.0 is asked to read environment variables, via getenv,
> it always decodes the underlying octet string according to the current
> locale's nominal character encoding. This is a problem, because the
> environment variable's value is not necessarily encoded that way, and
> may not even be an encoding of a character string at all. The decoding
> is lossy, where the octet string isn't consistent with the character
> encoding, so the original octet string cannot be recovered from the
> mangled form. I don't see any Scheme interface that retrieves the
> environment without locale decoding.
Options:
Add optional "encoding" arg to scm_getenv; encoding is a string
Add alternate getenv interface that returns a bytevector
We'll have to do the same for setenv too, I think.
I think I would go with adding an encoding argument to getenv. WDYT
Mark and Ludovic?
Andy
next prev parent reply other threads:[~2016-06-24 5:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 4:17 bug#20822: environment mangled by locale Zefram
2015-06-16 6:26 ` John Darrington
2015-06-16 20:03 ` Andreas Rottmann
2015-06-16 20:50 ` John Darrington
2016-03-04 23:22 ` Zefram
2016-06-24 5:57 ` Andy Wingo [this message]
2016-06-26 1:10 ` Mark H Weaver
2016-06-26 10:33 ` Zefram
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=87eg7njfhk.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=20822@debbugs.gnu.org \
--cc=ludo@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).