From: Andy Wingo <wingo@pobox.com>
To: mhw@netris.org, ludo@gnu.org
Cc: 20823@debbugs.gnu.org, Zefram <zefram@fysh.org>
Subject: bug#20823: argv mangled by locale
Date: Fri, 24 Jun 2016 08:11:29 +0200 [thread overview]
Message-ID: <87a8ibjeum.fsf@pobox.com> (raw)
In-Reply-To: <20150616043300.GB2718@fysh.org> (zefram@fysh.org's message of "Tue, 16 Jun 2015 05:33:00 +0100")
On Tue 16 Jun 2015 06:33, Zefram <zefram@fysh.org> writes:
> I don't see any Scheme interface that reliably retrieves the command
> line arguments without locale decoding.
[...]
> The actual data passed between processes is an octet string, and
> there really needs to be some reliable way to access that octet string.
> My comments about resolution in bug#20822 "environment mangled by locale"
> mostly apply here too, with a slight change: it seems necessary to store
> the original octet strings and decode at the time program-arguments is
> called. With that change, the decoding can be responsive to setlocale
> (and in particular can reliably use ISO-8859-1 in the absence of
> setlocale).
Proposal: scm_i_set_boot_program_arguments just copies the bytes, and
scm_program_arguments decodes them. I don't know whether to save the
locale that was current at program start and use that locale to decode
the arguments, or default the current locale, or what. I also don't
know whether to supply an optional "encoding" argument, and use that
encoding to decode the command line arguments. Thoughts, Mark and
Ludovic?
Andy
next prev parent reply other threads:[~2016-06-24 6:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 4:33 bug#20823: argv mangled by locale Zefram
2016-03-04 23:24 ` Zefram
2016-06-24 6:11 ` Andy Wingo [this message]
2016-06-24 8:42 ` Zefram
2016-08-14 21:36 ` 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=87a8ibjeum.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=20823@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=mhw@netris.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).