Hi,
I am a bit of a newbie with encodings...
I know that sqlite supports 2 kinds of encodings natively at the moment.
These encodings are ISO-8859-1 and UTF8. The choice of encoding is set at
compile time.
As far as I understand, UTF-8 will read 8859-1 without problem but
ISO-8859-1 will not be able to read UTF-8, unless everything in the UTF8
string uses only 8859-1 codes.
So, the best choice for compatibility and portability seems to be UTF8.
Unfortunately, PHP for example, ships a version of sqlite that is 8859-1
compiled, this means that a lot of people are going to use sqlite with this
charset, without knowing they could benefit from UTF8. So at the moment, I
prefer to stick with ISO-8859-1 in my desktop application.
I have tried to insert the euro symbol in a column and it came out as '?'
Do you have any idea about what is causing this ?
I have read that the euro symbol was supported in an extension of the 8859-1
charset (), is it also supported by sqlite or do I have to switch to UTF8,
something I would like to avoid at the moment (waiting for Sqlite 3 ;) ).
Can you confirm that you don't have any problems with the euro symbol in
your own applications, using 8859-1.
BTW, my desktop app runs on MACOSX so I first convert the user input from
MacRoman to ISO-8859-1, which works fine with accents, then runs it through
sqlite_mprintf("%q", myCString) to escape the string. Before displaying
again the string, I convert it back from 8859-1 to MacRoman.
Thanks for any advices,
Bertrand Mansion
Mamasam
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
