|
From: | lilypond |
Subject: | Re: Issue 2173 in lilypond: Deal with file names not encoded in UTF-8 |
Date: | Tue, 03 Jan 2012 09:44:18 +0000 |
Comment #2 on issue 2173 by address@hidden: 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?
[Prev in Thread] | Current Thread | [Next in Thread] |