[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Filename encoding
From: |
Eli Zaretskii |
Subject: |
Re: Filename encoding |
Date: |
Thu, 16 Jan 2014 18:09:33 +0200 |
> From: address@hidden (Ludovic Courtès)
> Cc: address@hidden
> Date: Thu, 16 Jan 2014 14:03:05 +0100
>
> Eli Zaretskii <address@hidden> skribis:
>
> >> From: address@hidden (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.
- Re: Filename encoding, (continued)
- Re: Filename encoding, Mark H Weaver, 2014/01/15
- Re: Filename encoding, Chris Vine, 2014/01/15
- Re: Filename encoding, Eli Zaretskii, 2014/01/15
- Re: Filename encoding, Ludovic Courtès, 2014/01/15
- Re: Filename encoding, Eli Zaretskii, 2014/01/15
- Re: Filename encoding, Ludovic Courtès, 2014/01/16
- Re: Filename encoding, John Darrington, 2014/01/16
- Re: Filename encoding, Eli Zaretskii, 2014/01/16
- Re: Filename encoding,
Eli Zaretskii <=
- Re: Filename encoding, Mark H Weaver, 2014/01/16