Database corrupt, bug in VarCharField with utf8?

[Steve Albin]

On Monday, June 8, 2009 sunshine at public.kherson.ua (Ruslan Zasukhin) wrote:

>> I'm curious. Since I know nothing about UTF encoding and would rather not
>> study it and I believe there may be other users out there who have a similar
>> mental challange... Why can't Valentina default to an encoding method that
>> works. Perhaps UTF16?
>
>Hey, on DEFAULT Valentina creates UTF-16
>All right here
>
>But sometimes developers who know unicode
>Try to use UTF8, because for English and Roman languages
>It is one byte per char.

Does Valentina automatically convert to UTF16 from UTF8 when adding data to a table.  REALbasic defaults to UTF8.  Should I be converting strings to UTF16 before adding and updating records?  Or is this done automatically?

I'm not doing anything now and things apparently work, but maybe I'm lucky.  

OT - Is it me, or does anyone else notice that in this list and the RB list, the questions of handling encodings seems to be the most misunderstood programming issue.

Steve


-- 
Steve Albin - Montclair, NJ
http://www.jazzdiscography.com/
http://www.steve-albin.com/