Database corrupt, bug in VarCharField with utf8?

[Ruslan Zasukhin]

On 6/8/09 2:50 PM, "william humphrey" <bill at bluewatermaritime.com> wrote:

Hi William,

> 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.

> And since UTF-8 does not work why is that option  allowed?

Historical :)

> Or at least why isn't there an error message that comes up if you
> choose UTF-8 encoding that says something like "Don't use this unless you are
> willing to put up with some errors?"

Yes, may be we should make error msg for now
Until it is fixed
 
> Bill
> 
> I'm asking this because I don't even know how to check how my database is
> encoded but I hope it is UTF-16

Yes it is,

You can check right in Vstudio,
    select DB object, see properties inspector
        


-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]