Filenames with Win32 special characters (or: Interix filename compatibility)

Brian Dessent
Wed Mar 12 16:20:00 GMT 2008

Corinna Vinschen wrote:

> I don't see that this filename is printed correctly according to the
> meaning of these characters in Explorer on Windows XP.
> Rather, it looks like all filenames with strange chars:

That's odd, the display in Explorer (XP) is correct for me for \x0331. 
(Not for the other one, that one looked all crazy and I wasn't actually
suggesting to use it.)

But that's kind of a secondary issue really.  The main problem with this
scheme that I encountered was that if you tried to open a file with
\xf0xx codepoints in its filename with an ANSI app, those characters
would translate to just '?' in cp1252 and the ANSI app would fail to
open the file.  That's a regression from what we have now in that when
using managed mounts, the filenames are garbled but you can at least
open/save/edit them normally with any app.  That is what intrigued me
about \x0331, in that it translated to plain _ in cp1252 so that the
files remained totally accessible to any app.

> The hash character acting as this box char printed for unknown character
> values.  If I switch the font, I can get a trailing underscore for the
> 0x0331 character.  I didn't find a font which shows this correctly as
> half width underscore under the preceding character.  No font printed
> the 0x034f character other than as a box.

I am using Segoe UI as the font in Explorer here.  But clearly we can't
rely on such details.


More information about the Cygwin-developers mailing list