Hi, Mistachkin Thanks for you fix the shell There is still some issue in the sqlite shell, in windows sqlite3_open need file name encoding with utf-8, and fopen need ansi , if the file name in command line include multi-byte characters, there will be a problem, eg
Shell.exe ???.db // not work, sqlite3_open need utf8 string In the sqlite shell: sqlite>.open ??.db //work fine, because the string ???.db" encoding with utf8,and sqlite3_open take it sqlite>.read ??.sql //not work , fopen need filename with ansi characters ________________________________ ???: Joe Mistachkin<mailto:sqlite at mistachkin.com> ????: ?2016/?1/?1 4:08 ???: 'SQLite mailing list'<mailto:sqlite-users at mailinglists.sqlite.org> ??: Re: [sqlite] Do you mean utf8_fprintf on this commit ? Domingo Alvarez Duarte wrote: > > On this commit https://www.sqlite.org/src/info/8cf01fff232d15d3 do you > mean "utf8_fprintf" instead of "utf8_printf" ? > No, I meant to use the existing "utf8_printf" function (and the new "raw_printf" macro). -- Joe Mistachkin _______________________________________________ sqlite-users mailing list sqlite-users at mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
