Version 3, now in trunk, is totally "wide path" under Windows, at least with the Microsoft supplied standard library. And even with Cygwin, everything is totally wide path except that wide paths in file opens are converted to narrow paths for the actual i/o stream call.
Question: Can I write: boost::filesystem::fstream f("שלום.txt",std::ios_base::out); When "שלום.txt" is UTF-8 string and Unicode file name will be created? If so, way to go. If you suggesting: boost::filesystem::fstream f(L"שלום.txt",std::ios_base::out); Then this is not what I'm talking about. I'm not talking about "Wide" path -- this is exectly what I was writing "nowide" make a library compatible with C/C++ **standard** functions like std::fstream::open(char const *,...) or std::fopen(char const *,...) but be fully Unicode enabled (utf-8) as they are on all-other operating systems without all "wide" api. Is somebody interested? Artyom