"Vinnie" <thev...@yahoo.com> wrote in message news:320060.55321...@web58204.mail.re3.yahoo.com > However, I have table fields which will be UTF-16. For example, > filenames that have to support international character sets. Or > metadata fields that use different character sets (UNICODE). For > these I am using sqlite3_bind_text16() and passing an appropriate > wchar_t buffer. > > On the other hand there is some legacy data that I want to store > using UTF-8. For these fields I will use sqlite3_bind_text(). It is > possible that in a single INSERT statement there are both UTF-16 and > UTF-8 (wchar_t and char) fields present.
Note that both UTF-8 and UTF-16 are capable of representing the full range of Unicode characters. Conversion between the two is lossless. You seem to be under impression that UTF-8 is somehow deficient, only suitable for "legacy" encoding. This is not the case. Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
