John Crenshaw wrote: > Similarly, UTF-16 is NOT the same as UCS-2 (the wide "Unicode" chars > used by MS APIs)
Win32 API does too support UTF-16. What makes you believe otherwise? > though it looks the same at low values. UTF-16 is a > multibyte character set, while UCS-2 is always 2 bytes per character. > You have to convert these values. Every valid UCS-2 string is also a valid UTF-16 string. Some UTF-16 strings (those containing surrogate pairs) cannot be represented in UCS-2 (which can be thought of as UTF-16 sans surrogate pairs). So a) why do you feel such a conversion is necessary in the first place, and b) how exactly do you propose it be performed? Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
