On Thursday 19 May 2005 00:53, Beman Dawes wrote:
and values of LC_ALL, LC_CTYPE and LC_LANG variables. But then it contains its own translation tables. So using locale("") is the best guess, I think.
OK, I've added wpath_traits::imbue() functions so the user can control the locale to get the conversion facet. If the user doesn't call imbue(), the default will be the global locale at the time of first use of a wpath conversion. But see below.
Good.
So using locale("") is the best guess, I think.
After reading the C++, C, and POSIX standards, I would say you are right. But wide_test got a conversion failure from the codecvt facet on the Mac. Ditto for the global locale. I haven't tested on POSIX yet.
Looking at the test, it creates various files with various funny names. So, if locale("") is not unicode, you'll indeed get conversion failures. Or do I miss something? - Volodya