Am Sonntag 28 März 2010 13:10:17 schrieb Michael Wild: > The easy fix? Only use ASCII characters in your path names... > > The real fix would be to port CMake to fully support UTF-16/32: a huge > undertaking, with any software. Especially, since wchar_t is not > guaranteed to be large enough to hold unicode characters; it may be as > small as 8 bit!
See http://www.opengroup.org/onlinepubs/7990989775/xsh/stddef.h.html Even when sizeof(wchar_t)==1, you don't have a problem. But since there is no easy and standard way to convert from wchar_t to Unicode (of the locale character set is not UTF-8), whar_t is useless if you need to explicitely convert to non-locale character sets. Else, it is sufficient. This is also a bit dedicated to the strange Windows environment... :-( > On many platforms, most compilers use 32 bit, but you > can't rely on that. The upcoming C++ standard (C++0x) does define > exact-width character types (char16_t, char32_t) and the corresponding > string types (std::u16string and std::u32string), but then I don't know > about the whole machinery you need to actually deal with such strings > effectively. C++0x would definitely be nice but will still need several month. gcc-4.5 and VC++ 2010 wil partly support it but you can add several years before it is widely adopted. HS _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
