>
> Irony aside, you wouldn't believe how many systems claiming to be i18n
> aware fail miserably when handling other than Latin-1 charsets
> (especially in filenames).
>
> If Costas can provide a patch, I think it'd be a useful addition to
> the SQLite's Win32 file handling. I'm not sure that op
On 8/8/06, John Stanton <[EMAIL PROTECTED]> wrote:
Our Sqlite applications work not only on Win98 and Win2000 but also on
Linux, AIX and Solaris. Where did we go wrong?
Irony aside, you wouldn't believe how many systems claiming to be i18n
aware fail miserably when handling other than Latin-1
lite-users@sqlite.org
Subject: Re: [sqlite] Problems opening db in win9x and utf8 filename
Our Sqlite applications work not only on Win98 and Win2000 but also on
Linux, AIX and Solaris. Where did we go wrong?
Costas Stergiou wrote:
Hi all,
I saw no more comments on this suggestion. It is very
work on both of these OSs, but with
external manipulation.
> -Original Message-
> From: John Stanton [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 08, 2006 11:13 AM
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] Problems opening db in win9x and utf8 filename
PM
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] Problems opening db in win9x and utf8 filename
I no longer have a win98 system to test with, but based on my
understanding...
os_win.c attempts to convert the filename from UTF-8 to UTF-16. If it
succeeds, it calls CreateFileW;
Actually
any
ansii char in the filepath.
Costas
> -Original Message-
> From: Costas Stergiou [mailto:[EMAIL PROTECTED]
> Sent: Saturday, August 05, 2006 11:47 PM
> To: sqlite-users@sqlite.org
> Subject: RE: [sqlite] Problems opening db in win9x and utf8 filename
>
>
> >
&
>
> I no longer have a win98 system to test with, but based on my
> understanding...
>
> os_win.c attempts to convert the filename from UTF-8 to UTF-16. If it
> succeeds, it calls CreateFileW;
Actually, there is a flag there that caused the convertion to UTF-16 to
'fail' (it doesn't really fai
On 8/5/06, Costas Stergiou <[EMAIL PROTECTED]> wrote:
According to the docs, the file path should be utf8 encoded. If in the path
there are non-ansii chars, the following method fails in win98.
Tried the following:
1. Created an sqlite3 db in a path containing greek chars
2. Tried to open it by
On 8/5/06, Costas Stergiou <[EMAIL PROTECTED]> wrote:
Hello,
I am encountering a problem trying to open a sqlite3 db (ver 3.3.6) using
the sqlite3_open function.
According to the docs, the file path should be utf8 encoded. If in the path
there are non-ansii chars, the following method fails in wi
Hello,
I am encountering a problem trying to open a sqlite3 db (ver 3.3.6) using
the sqlite3_open function.
According to the docs, the file path should be utf8 encoded. If in the path
there are non-ansii chars, the following method fails in win98.
Tried the following:
1. Created an sqlite3 db in a
10 matches
Mail list logo