>My main point is that you can't take the UTF-16 string and safely supply
>it to APIs which want UCS-2 encoded text, such as Win32 APIs (including
>things like SetWindowText()). Odds are that the only library you are
>using which supports UTF-16 is SQLite. You should always be converting
>the text to UCS-2 before you use it.

Certainly not!

Win32 supports full Unicode 5.1 in UTF-16 for a long time.



_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to