John Crenshaw wrote: > 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()).
What makes you believe Win32 API, and SetWindowText in particular, does not support surrogate pairs? Win32 API works just fine with UTF-16. > Odds are that the only library you are > using which supports UTF-16 is SQLite. You must be confusing UTF-16 with something else. I can't think of any decent library that supports UCS-2 but not UTF-16. > You should always be converting > the text to UCS-2 before you use it. How precisely would you suggest to do that? What would you do with surrogate pairs - just drop them on the floor? Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
