[V4RB] UTF8 vs. UTF16

[Jörg Pressel]

To tell the whole story – the source data is actually UTF16. I  
converted that to UTF8 and stored it to the db.

I need fast db writing – so should I use the UTF16 I have and hand it  
over to Valentina?

Thanks,

Jörg


> On 3/22/06 11:33 PM, "Jörg Pressel" <joergp at three-2-one.com> wrote:
>
> Hi Jörg,
>
>> I'm still converting my app to V4RB2 ...
>> In earlier versions I stored strings in UTF8 format (though V4RB1 did
>> not support it directly) – what I've read Valentina 2 uses UTF16
>> internally.
>>
>> Do I have to store strings in UTF16 format to the database or does
>> Valentina automatically convert all strings to UTF16?
>
> NO.
>
> Just send strings to Valentina AS IS.
>
> REALBasic uses UTF8 encoding on default, and this is what V4RB
> expect to see now.
>
>> If it's not necessary I guess writing UTF16 strings to the db would
>> be faster, because it's the internal string format – right?
>
> Not right. Mainly no difference.
> May be even faster if we will do this in our C++ code