Comment #2 on issue 2173 by d...@gnu.org: Deal with file names not encoded in UTF-8
http://code.google.com/p/lilypond/issues/detail?id=2173
<URL:http://msdn.microsoft.com/en-us/library/x99tb11d%28v=VS.100%29.aspx> appears to suggest that Windows can't to UTF-8. If that's true, we will need to recode UTF-8 into UTF-16 (as the easiest option, probably not supporting 21-bit Unicode with surrogates as that would be of comparable complexity as UTF-8 is) and back again for accessing file names. Or writing to the terminal. Or pretty much anything else.
I have a hard time really believing that. But then I tend to have a hard time believing a lot of things about Windows.
Anybody with an actual Windows system who could corroborate one way or the other?
_______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
