> -----Original Message----- > From: Austin Ziegler [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 04, 2005 2:12 PM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] International Language Support
[snip] > If you're compiling with UNICODE and are using TCHAR*, you'll > be getting wchar* (or std::wstring), which is actually UCS-2 > (related in some way to UTF-16, but again not *quite* the > same since UCS-2 doesn't support surrogates). This is better > than ANSI/OEM, but not by much because it causes other problems. The UNICODE support in Windows is completely agnostic with regard to supporting surrogates. 16-bit is, afterall, 16-bit. It's only when Windows attempts to *render* the text that any concerns over surrogates arises. Here's a little blog post regarding it: http://blogs.msdn.com/michkap/archive/2005/05/11/416552.aspx Robert
