Thanks for the infos.
__
If you reply to this email, your message will be added to the discussion below:
http://sqlite.1065341.n5.nabble.com/How-to-search-for-fields-with-accents-in-UTF-8-data-tp96249p96294.html
This email was sent by Winfried (via Nabble)
To
> Le 20 juin 2017 à 20:04, Scott Robison a écrit :
>
> Regardless, I prefer UTF-8 to UCS-2 / UTF-16. Microsoft has certainly
> had time to make their interfaces more UTF-8 friendly. I just don't
> think they get enough credit for committing to Unicode in an era when
> few were.
We are in full ag
On Tue, Jun 20, 2017 at 8:17 AM, Olivier Mascia wrote:
>> Le 20 juin 2017 à 15:24, R Smith a écrit :
>>
>> As an aside - I never understood the reasons for that. I get that Windows
>> has a less "techy" clientèle than Linux for instance, and that the backwards
>> compatibility is paramount, and
On Tuesday, 20 June, 2017 07:24, R Smith wrote:
> Every lesson is valuable! Just to be clear - there is nothing wrong
> with using the CLI. When pointing it to a file that is correctly encoded
> the import must work correctly (if not, it's a bug) - It's just
> difficult to enter weird and wonder
> Le 20 juin 2017 à 15:56, Simon Slavin a écrit :
>
> The console you see is pretty-much the one which was in Windows 3.1. It does
> not use the modern API written post-unicode, it calls the old
> single-character Windows routines which are still in Windows so old programs
> don’t suddenly st
> Le 20 juin 2017 à 15:24, R Smith a écrit :
>
> As an aside - I never understood the reasons for that. I get that Windows has
> a less "techy" clientèle than Linux for instance, and that the backwards
> compatibility is paramount, and that no console command ever need fall
> outside the 7-bit
Simon Slavin-3 > To clarify the clarification, you can use the SQLite
shell tool just fine as long as you use it to process files, rather than
expect characters which are entered through the keyboard or shown on the
display to work. So use ".read" or ".output" or ".once", and then use a
non-c
On 20 Jun 2017, at 2:24pm, R Smith wrote:
> Every lesson is valuable! Just to be clear - there is nothing wrong with
> using the CLI. When pointing it to a file that is correctly encoded the
> import must work correctly (if not, it's a bug) - It's just difficult to
> enter weird and wonderf
R Smith >
>> 2. Do not use the sqlite3.exe CLI if the data use anything more than
>> the basic latin alphabet. Instead, use a GUI application (eg. for
>> Windows, SQLite Studio, SQLitespeed, etc.)
> Every lesson is valuable! Just to be clear - there is nothing wrong
with using the CLI. When po
Indeed. Technically-minded Windows users do exist (Hi, Microsoft, I'm right
here!), and I have neither the time nor the inclination to learn PowerShell
when the Windows terminal is already adequate---with a set of ports of GNU
tools, anyway. :)
On June 20, 2017 9:24:12 AM EDT, R Smith wrote:
>
On 2017/06/20 2:34 PM, Gilles wrote:
Lessons I learned:
1. In CSV files, double-check how data are encoded
2. Do not use the sqlite3.exe CLI if the data use anything more than
the basic latin alphabet. Instead, use a GUI application (eg. for
Windows, SQLite Studio, SQLitespeed, etc.)
Ever
Posted by David Raymond on Jun 19, 2017; 5:22pm > /The Windows command
prompt and unicode have always not played well with each other. SQLite
itself works perfectly with data on disk or in the database, there are
just translation and display problems when going to and from the command
prompt. /
The Windows command prompt and unicode have always not played well with each
other. SQLite itself works perfectly with data on disk or in the database,
there are just translation and display problems when going to and from the
command prompt.
If you write out your query in, say, Notepad++ and s
> Le 19 juin 2017 à 15:20, Simon Slavin a écrit :
>
> On 19 Jun 2017, at 11:13am, Gilles 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
fields with accents in UTF-8 data?
Found the problem: Turns out the CSV file isn't in UTF8 but in CP1252 :-/
Icon.exe can be used to convert a file before importing it in SQLite.
https://dbaportal.eu/2012/10/24/iconv-for-windows/
Thanks everyone for the
Found the problem: Turns out the CSV file isn't in UTF8 but in CP1252 :-/
Icon.exe can be used to convert a file before importing it in SQLite.
https://dbaportal.eu/2012/10/24/iconv-for-windows/
Thanks everyone for the help.
___
sqlite-users mailing li
On 19 Jun 2017, at 11:13am, Gilles 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 Unicod
Thanks everyone.
It looks running sqlite3.exe in a terminal window (CMD) in Windows 7
doesn't work: Apparently, it doesn't support UTF-8.
And when using DB Browser for SQLite, it does work only if I copy/paste
the output with the "?" where an accented character lives:
https://s15.postimg.org
sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im
Auftrag von CC
Gesendet: Sonntag, 18. Juni 2017 12:53
An: sqlite-users@mailinglists.sqlite.org
Betreff: [sqlite] How to search for fields with accents in UTF-8 data?
Hello
I imported a CSV file where data are encoded in UTF-8.
For some applications it is, for others not in all cases. For "just" accented
characters it should be no problem following these instructions.
General advice: download OpenOffice or similar OpenSource packages. They are
completely free and support almost all OS's.
Kind regards | Vriendelijke gro
You can even make UTF-8 the default encoding in Windows as it is in SQLite
https://superuser.com/questions/239810/setting-utf8-as-default-character-encoding-in-windows-7
CC wrote on Sun, 18 Jun 2017 12:52:33 +0200:
>As an alternative, I tried SQLite Studio, but it fails:
;>Returns no record
>S
Dear CC:
I use Spanish language, with letters with accents.
When I try to import from a .csv the data obtained in the table was "rare" and
I have to implement some routines to convert "What the program read to the
letter I want to write", and I solve the problem. I think in a prehistory way.
I
CC wrote:
> I imported a CSV file where data are encoded in UTF-8.
>
> Some of the characters (like Î) are not available in the ASCII table, so I
> can't use the CLI sqlite3.exe to search.
The latest version of sqlite3.exe might work.
Anyway, to check that whatever tool you're using uses Unicode
Hello
I imported a CSV file where data are encoded in UTF-8.
Some of the characters (like Î) are not available in the ASCII table, so
I can't use the CLI sqlite3.exe to search.
As an alternative, I tried SQLite Studio, but it fails:
;Returns no record
SELECT COUNT(*) FROM MyTable WHERE REGIO
24 matches
Mail list logo
