2011/1/17 Mathias Fröhlich <[email protected]>: > Which means all the wchar_t interfaces in windows also work > for really all languages' character sets. The same holds for the usual linux > 32 bit wchar_t which is also sufficient for all known unicode glyphs. > Using these functions appears to me the most system compatible way. They just > implement the systems way of handling character encoding. You do not need to > know anything how this is done.
Um, actually no. wchar_t on Unix is doesn't have to be 32 bit, you do not know what kind of encoding the system uses internally (the C/C++ standard doesn't say what it should be!) This is one of the reasons why people recommend to forget about wchar_t on Unix and just use char_t and UTF-8 encoding explicitly, converting as needed. It has also the advantage of keeping the compatibility with other tools/libraries that cannot handle wide strings, but multibyte encodings (UTF-8) are transparent for them. Yeah, Unicode is a major pain :( Regards, Jan _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
