17 Jun
2010
17 Jun
'10
7 a.m.
I'm saying that Filesystem v3 on Windows doesn't interpret narrow strings as UTF-8 by default. Beman said that it did...
There is a misunderstanding here. V3, like any Windows program, by default interprets narrow strings according to the File code page. You have to configure that yourself if you want it to be UTF-8.
Windows does not support UTF-8 code page at all (actually it is only supported as parameter of WideToMultibyte/MultibyteToWide)
Agreed. If anyone wants to submit a patch for glibc++/MinGW that uses the wide Windows API, that would be a better solution.
This is not a bug. And there is nothing to fix. std::fsteambuf::open(wchar_t const *,..) is not standard but Microsoft Specific extension . Artyom