-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jean-Christophe Deschamps wrote:
> A much better solution is to use a MSYS terminal (installed by MinGW),
> so you have UTF-8 command-line and data entry/display without
> conversion. No need to "patch" anything.
No need for msys. You can make a r
Hello Jean-Christophe,
JCD> If you change input encoding and use your code page, then it's likely
JCD> you'll going to do the same with data, which is plain wrong: SQLite
JCD> needs UTF-8 (or UTF-16) data, not ANSI.
Yeah, I solved this long ago by simply insuring I always used UTF-8
encoding on
>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 tha
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.
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 sqlite
5 matches
Mail list logo
