Per Bernhardsson wrote:
Windows uses UCS2 which is very similar to UTF-16 but not the same.
See here<http://en.wikipedia.org/wiki/UCS2>for more information. So a
wchar_t * might point to a UCS2 string just as
well as a UTF-16 string. Assuming they are the same can (admittedly very
rarely) lead to unwanted results.
UCS-2 is a proper subset of UTF-16, so all legal UCS-2 strings are legal
UTF-16 strings. In addition, the many Windows APIs are well on their way
to accepting UTF-16, so soon, even that won't be a problem:
http://blogs.msdn.com/michkap/archive/2005/05/11/416552.aspx
Can you be more specific about what you think these rare, unwanted results
might be?
Dave
