V4RB b3 uploaded

[jda]

>
>  > Yes -- select Russian from the International control panel and type
>>  into a RB editfield -- works.
>
>This raise question:
>
>     will then all RB strings work not in UTF8 encoding,
>     but in Cyrilic-MAC (single byte) ?
>
>What about your Herbew test?
>
>This is not questions to you.
>Just thinking aloud.
>
>If they are not in UTF8 then this explain.
>Because now V4RB simply expect UTF8 and do not check real encoding of
>REALstring. I will add that later.
>

The default encoding for all RB strings is now utf-8. The Cyrilic, 
Hebrew, Greek, etc. are all utf-8. This includes string literals, 
which is what you are using in the beta examples.

What I meant above was NOT that Cyrilic text works in Valentina 2.0 
examples -- I meant Cyrilic is entered into *RB* apps (and code 
editor in the IDE) as unicode correctly, which is what I thought you 
were asking.

So, there is still a problem with 2.0.

Ruslan, you should try this yourself -- it's a matter of a few 
seconds to add multibyte UTF-8 characters to a table or field name 
and run the example.

Jon