From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: Filename encoding
Date: Thu, 16 Jan 2014 00:29:06 +0100 [thread overview]
Message-ID: <87a9ewu8n1.fsf@gnu.org> (raw)
In-Reply-To: 20140115195051.3272023c@bother.homenet
Chris Vine <chris@cvine.freeserve.co.uk> skribis:
> So far as filenames are concerned,
> this seems to me to be something for which a fluid would be just the
> thing - it could default to the locale encoding but a user could set it
> to something else. I suppose command lines and environmental variables
> are less problematic because they are usually local to a particular
> machine, although that may not necessarily be so true these days for
> command lines.
I makes some sense to have a fluid for that.
That said, it’s not so great either: for each Unicode-capable library in
use, people would end up define $THELIB_FILE_NAME_ENCODING. Apart from
GLib, I think language run-time supports (Python, etc.) typically assume
locale encoding too, no?
Does anyone know of systems where the file name encoding is commonly
different from locale encoding? Is it the case on Windows?
Ludo’.
next prev parent reply other threads:[~2014-01-15 23:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 12:52 Filename encoding Chris Vine
2014-01-15 18:14 ` Mark H Weaver
2014-01-15 19:02 ` Eli Zaretskii
2014-01-15 21:34 ` Mark H Weaver
2014-01-16 3:46 ` Eli Zaretskii
2014-01-15 19:50 ` Chris Vine
2014-01-15 21:00 ` Eli Zaretskii
2014-01-15 21:42 ` Chris Vine
2014-01-16 3:52 ` Eli Zaretskii
2014-01-15 21:47 ` Mark H Weaver
2014-01-15 22:32 ` Chris Vine
2014-01-16 3:55 ` Eli Zaretskii
2014-01-15 23:29 ` Ludovic Courtès [this message]
2014-01-16 4:00 ` Eli Zaretskii
2014-01-16 13:03 ` Ludovic Courtès
2014-01-16 14:07 ` John Darrington
2014-01-16 16:12 ` Eli Zaretskii
2014-01-16 16:09 ` Eli Zaretskii
2014-01-16 15:36 ` Mark H Weaver
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=87a9ewu8n1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-user@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).