Re: guile can't find a chinese named file

[Eli Zaretskii]

> From: Marko Rauhamaa <address@hidden>
> Cc: address@hidden,  address@hidden
> Date: Thu, 16 Feb 2017 09:02:09 +0200
> 
> Eli Zaretskii <address@hidden>:
> 
> >> From: Marko Rauhamaa <address@hidden>
> >> Cc: address@hidden,  address@hidden
> >> Date: Thu, 16 Feb 2017 08:15:57 +0200
> >> 
> >> It is possible to have illegal Unicode even in Windows filenames, ie,
> >> filenames not expressible using Guile's strings.
> >
> > Is it really possible? Can you show a code example that would create
> > such an illegal filename on Windows?
> 
> I have rely on hearsay since I don't have Windows at my disposal:
> 
>    NTFS allows any sequence of 16-bit values for name encoding (file
>    names, stream names, index names, etc.) except 0x0000.
> 
>    <URL: https://en.wikipedia.org/wiki/NTFS#Internals>
> 
> Not all sequences of 16-bit values are legal UTF-16.

Of course.  But unlike on Unix, it is much harder to create such file
names, because Windows APIs won't allow that.  You probably will have
to access the directory entries on a very low level.

Anyway, this is not the issue at hand.  I only mentioned UTF-16
encoding on Windows because Tomás thought file names on Windows can be
encoded in several different encodings.