> They have a 16-bit > type called 'wchar_t' which cannot accomodate all characters since > Unicode 3.1. So what they will likely end up doing is to use UTF-16 > as an encoding for 'wchar_t *' strings,
As far as I am aware, that's what's *already* the case. It may be
unfortunate that the type is called wchar_t, but it's much too late
to change that for that platform.
/kent k
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
