Consider upgrading to 3.3.6. The following are some changes related to the
UTF stuff.
*2006 June 6 (3.3.6)*
- Fix an obscure segfault in UTF-8 to UTF-16 conversions
*2006 April 5 (3.3.5)*
- The sqlite3_create_collation() function honors the
SQLITE_UTF16_ALIGNED flag.
On 8/4/06,
On 8/3/06, Cory Nelson <[EMAIL PROTECTED]> wrote:
I recommend using utf-16 in the database - sqlite doesn't fully
support utf-8, and some things may give unexpected results if you use
it.
As with others who have replied, I have not had a problem working with
UTF8 in a SQLite database.
Cory Nelson wrote:
I recommend using utf-16 in the database - sqlite doesn't fully
support utf-8, and some things may give unexpected results if you use
it.
Could you expand a bit on this please?
I haven't seen any bugs as such with sqlite as such but I did have a few
problems storing
On 8/4/06, Cory Nelson <[EMAIL PROTECTED]> wrote:
I recommend using utf-16 in the database - sqlite doesn't fully
support utf-8, and some things may give unexpected results if you use
it.
Could you give some example of unexpected result with UTF-8?
In my experience the only unexpected results
On 8/3/06, RohitPatel <[EMAIL PROTECTED]> wrote:
Hi Dennis Volodomanov
I am using SQLite 3.3.4.
My Win32 Application needs international language support (Chinese,
Japanese).
I need my Win32 Application to build such that,
MBCS defined for Windows 98/ME and
UNICODE (and _UNICODE) defined
Hi Dennis Volodomanov
I am using SQLite 3.3.4.
My Win32 Application needs international language support (Chinese,
Japanese).
I need my Win32 Application to build such that,
MBCS defined for Windows 98/ME and
UNICODE (and _UNICODE) defined for Windows NT/2000/2003/XP.
Can you help me by
6 matches
Mail list logo
