Andy Wingo <wi...@pobox.com> writes:
> On Tue 16 Jun 2015 06:17, Zefram <zef...@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?
I just don't see how this could be used sanely in actual practice.
These things are conceptually strings, and by convention they are
supposed to encoded in the locale encoding. If that convention is
violated, I don't see what a program could do about it.
Can someone show me a realistic example of how this would be used in
practice?
Mark
