>I know nothing about the sqlite3 code, but if you can’t find unit tests doing
>non-ascii stuff, and you can't find conversion >code, than the original
>author(s) probably just didn’t implement it.
>
>I might be wrong, but that would be a shame, since utf-8 encoding/decoding is
>fully supported
Hi Michel,
On 24 Nov 2013, at 19:25, Michel wrote:
> Hi everyone,
>
> I have a sqlite3 data base which is UTF8 encoded. Accessing to it with a ruby
> script gives me the right encoding for accented vowel, and doing an hexdump
> of the file too, but I get a strange one with the sqlite3 package
Hi everyone,
I have a sqlite3 data base which is UTF8 encoded. Accessing to it with a
ruby script gives me the right encoding for accented vowel, and doing an
hexdump of the file too, but I get a strange one with the sqlite3
package in pharo 2.0.
For example, for 'é' (UTF8 0xC3A9) I get 0xA6
