On Sat, Feb 14, 2015 at 2:23 AM, Peter Haworth wrote:
>
> My brain is too fried to figure out why this should be so my plan is to
> just always encode/decode stuff when importing/displaying.
>
Sorry for the slow reply, but I note your other post on your tentative move
to LC 7 and the gotchas alo
Always a good policy. For one it can’t hurt, and for another… well I don’t have
another.
Bob S
On Feb 13, 2015, at 10:23 , Peter Haworth
mailto:p...@lcsql.com>> wrote:
My brain is too fried to figure out why this should be so my plan is to
just always encode/decode stuff when importing/displa
Thanks Kay. I tried looking at the db with the Firefox SQLite Manager
plugin and sure enough it doesn't display correctly. In this case, the
accented characters simply aren't there.
I went back and imported the data again, this time encoding the data as
UTF8. Now it displays correctly in both SQ
I think that it depends from the collation declared for DB | table | fields
indatabase. I'm using UTF8 bin and have no problems with text full of accented
characters. They are the same in my application and any other, even phpmyadmin.
Marek
___
use-l
Have you looked at your data using another db management tool?
My own limited experience of dealing with UTF8 with LC 7 and sqlite is that
if I don't textEncode(data,"utf8") into SQLite and textDecode(data,"utf8")
out of the db, then although all the data goes and comes back OK, if I look
at the d
Continuing down the path of making SQLiteAdmin unicode compliant.
I just took a file with French characters in Mac OS Roman format and and
used SQLiteAdmin to import it into an SQLIte database set up for UTF8
encoding. The import procedure did no decoding or encoding just read the
file and used I
