sqlite3_open[_v2] accepts all filenames in UTF-8 (although it doesn't check for valid UTF-8 string). So CP_UTF8 cannot be changed anywhere.
OTOH maybe command line utility should have some logic of re-encoding of command line parameter from terminal encoding to UTF-8. But I'm not sure about that. Could you try to run sqlite3 from a batch file that is written in UTF-8 encoding (properly encode your path). I believe it will work this way... Pavel 2010/3/16 Kunc Filip <k...@medictech.com>: > Hello SQLite Team, > > > > We currently use sqlite 3.6.23. We have a big problem with characters with > accents or other special characters in path to database file, for example in > Czech Windows XP the "Application Data" folder is translated to "Data > aplikací" so if the accented 'í' is in path the sqlite3.exe writes that it > is unable to open file in this path. > > > > To workaround this problem we tried to find the source of this error. It > lies in MultiByteToWideChar and WideCharToMultiByte with CP_UTF8 as encoding > argument. If is instead used CP_ACP as ANSI encoding then there is no > problem. > > > > In attachment you will find diff patch which works for us. But because > SQLite3 source code is really big we can't be sure that this fix is correct > and doesn't introduce any side effects. > > > > Thanks for your hard work and help > > Filip Kunc > > > > > > > _______________________________________________ > sqlite-users mailing list > email@example.com > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > _______________________________________________ sqlite-users mailing list firstname.lastname@example.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users