RE: [sqlite] Problems opening db in win9x and utf8 filename

2006-08-08 Thread Costas Stergiou
> > 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

Re: [sqlite] Problems opening db in win9x and utf8 filename

2006-08-08 Thread Peter Cunderlik
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

Re: [sqlite] Problems opening db in win9x and utf8 filename

2006-08-08 Thread John Stanton
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 v

RE: [sqlite] Problems opening db in win9x and utf8 filename

2006-08-08 Thread Costas Stergiou
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

Re: [sqlite] Problems opening db in win9x and utf8 filename

2006-08-08 Thread John Stanton
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

RE: [sqlite] Problems opening db in win9x and utf8 filename

2006-08-08 Thread Costas Stergiou
if there is 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 > > > > &

RE: [sqlite] Problems opening db in win9x and utf8 filename

2006-08-05 Thread Costas Stergiou
> > 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

Re: [sqlite] Problems opening db in win9x and utf8 filename

2006-08-05 Thread Trevor Talbot
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

Re: [sqlite] Problems opening db in win9x and utf8 filename

2006-08-05 Thread Peter Cunderlik
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

[sqlite] Problems opening db in win9x and utf8 filename

2006-08-05 Thread Costas Stergiou
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