From: Eli Zaretskii <eliz@gnu.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-user@gnu.org
Subject: Re: Filename encoding
Date: Thu, 16 Jan 2014 18:09:33 +0200 [thread overview]
Message-ID: <83fvon3o3m.fsf@gnu.org> (raw)
In-Reply-To: <8738koaxkm.fsf@gnu.org>
> From: ludo@gnu.org (Ludovic Courtès)
> Cc: guile-user@gnu.org
> Date: Thu, 16 Jan 2014 14:03:05 +0100
>
> Eli Zaretskii <eliz@gnu.org> skribis:
>
> >> From: ludo@gnu.org (Ludovic Courtès)
> >> Date: Thu, 16 Jan 2014 00:29:06 +0100
> >>
> >> Does anyone know of systems where the file name encoding is commonly
> >> different from locale encoding? Is it the case on Windows?
> >
> > Windows stores file names on disk encoded in UTF-16, but converts them
> > to the current codepage if you use Posix-style interfaces like 'open'
> > and 'rename'.
>
> So in practice, given that Guile uses the POSIX interfaces, the
> assumption that file names are in the locale encoding is valid on
> Windows.
For now, yes. But I was under the impression that this thread
discusses future designs, and for that, I don't recommend to rely on
this situation to remain for long. After all, providing wrappers for
a few Posix interfaces is not such a hard job.
next prev parent reply other threads:[~2014-01-16 16:09 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
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 [this message]
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=83fvon3o3m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=guile-user@gnu.org \
--cc=ludo@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).