> Le 19 juin 2017 à 15:20, Simon Slavin <slav...@bigfraud.org> a écrit : > > On 19 Jun 2017, at 11:13am, Gilles <codecompl...@free.fr> wrote: > >> It looks running sqlite3.exe in a terminal window (CMD) in Windows 7 doesn't >> work: Apparently, it doesn't support UTF-8. > > Correct. And the "it" that doesn’t support UTF-8 is the Windows console. > SQLite works fine and handles everything as Unicode internally. The Windows > console won’t process multibyte characters internally and can’t display them > correctly. > > <https://msdn.microsoft.com/en-us/library/windows/desktop/dd317752(v=vs.85).aspx> > > "many legacy applications continue to use character sets based on code pages. > Even new applications sometimes have to work with code pages, often for one > of the following reasons: […] > • To communicate with the Windows Console, which does not support > Unicode." > > > Some people have found ways to hack around this, but they simulate compliance > for a certain codepage rather than implement UTF-8 globally. > > <https://www.curlybrace.com/words/2014/10/03/windows-console-and-doublemulti-byte-character-set/> > > "The Windows Console doesn’t support Unicode." > > <https://social.technet.microsoft.com/Forums/sharepoint/en-US/c42a0300-1803-475d-9438-d39e6672cc69/unicode-characters-in-powershell> > > Simon.
Switch the console I/O (windows only of course) of sqlite3 shell.c to use WriteConsoleW and ReadConsoleW, and there you go and forget about CHCP, codepages... Learned it the hard way last year, well after at some point I though DBCS would be enough. No. -- Best Regards, Meilleures salutations, Met vriendelijke groeten, Olivier Mascia, http://integral.software _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
