Rowan et al, On Fri, Jun 24, 2016 at 4:34 AM, Rowan Worth <row...@dugeo.com> wrote: > On 24 June 2016 at 16:13, Simon Slavin <slav...@bigfraud.org> wrote: > >> On 24 Jun 2016, at 5:04am, Igor Korot <ikoro...@gmail.com> wrote: >> >> > But everything should work independently of what code page is being used? >> >> The SQLite shell tool should work independently of the code page you have >> set. It should be translating strings from your current code page into >> Unicode. From your report it appears that it is not doing this, which >> means there's a bug in it. >> > > Thank you Simon for your voice of reason! > > For everyone else having a go at Igor, running the sqlite shell and typing > some characters into it does not constitute any claim about how those > characters are encoded. That's the operating system/application's concern.
I'm here in US and have only US_English version of Windows. IIUC here are couple of scenarios: Some guy in Germany (China, Japan) create SQLite db in the SQLite shell tool. (S)he also have German (Chinese, Japanese) version of Windows (localized). For whatever reason, (s)he decides to name all tables and fields in German (Chinese, Japanese). Now (s)he can inside the same tool do whatever - run queries (SELECT, INSERT, UPDATE), create triggers/stored procedures, etc. Because his/her OS/keyboard/drivers allows straight typing of native characters. Now this guy can send his/hers db file to me alone with some scripts to run. I should be able to open the db file on my US-English based Windows machine with SQLite command line tool withouit any issues and either load the script and execute it or open the script in notepad and copy/paste the queries into the SQLite shell tool. And here is the scenario #3. Here in US with US-English based Windows machine, I can add German language and start creating the database, tables and fields just like in the scenario 1. And I will also be able to run everything on the database. And I should be able to send my db file to my German friend and he will be able to also open such db and run queries. Are those 3 scenarios correct? If the answer is yes, will the code I posted in the original post work for all 3 of them? Or maybe just for the first one? Because if I'm in Germany, have the German version of Windows and the German keyboard, I don't need to type <ALT+225> to get that symbol. I will just type it on the keyboard. And if I have a German keyboard installed I also don't need to type <ALT+225> to get to this symbol. It might take me a while to find it on my English keyboard, but that's different story. ;-) The thing is - all I care about are those 3 scenarios, because only those are normal. Unfortunately I don't have an international version of Windows to test the database created with international characters appropriately and I don't want to add another keyboard layout. . So I tried to emulate it and it looks like I failed to create a proper test case. So, can someone please answer those questions. Thank you. P.S.: I may support the <ALT+nnn> scenario, but not right now. > > -Rowan > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
