Dean wrote:
> I'm not sure how many platforms that worst case scenario happens on, but
it
> could happen. Linux would probably be one, since it has a 32 bit wchar_t
and
> so its Iconv probably uses UCS-4 format.
iconv converts between two named encodings, so it can easily convert
directly from whatever to UTF-16. It has no straight forward way to
convert to wchar_t because there is no straight forward way of getting the
encoding used for wchar_t, or at least none that I've found.
The only reliable way in and out of wchar_t seems to be the mbstowcs
family of conversions, and these only convert from char * in an encoding
that depends on the current locale.
wchar_t seems more and more like it is best avoided altogether if
portability is of any concern at all.
Andy Heninger
IBM, Cupertino, CA
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
