[VREV] showing results

[Ruslan Zasukhin]

On 10/6/05 11:23 AM, "Ivan Smahin" <IvanSmahin at public.kherson.ua> wrote:

> Hello ron,
> 
> Thursday, October 6, 2005, 11:01:11 AM, you wrote:
> 
> rb> I would like to clarify the UTF16 UTF8 matter.
> rb> 1.  I cannot make a Val db of UTF 16 flds for REV
> rb> 2.  I can only pass UTF8 back and forth to REV (in its current
> rb> condition) through the V4REV xcmd.
> rb> 3. This is done by following the example provided in the IOEncoding
> rb> stack
> 
> rb> Correct?
> 
> Actually there is 3 stages where the encodings are involved.
> 
> 1. IOEncoding("UTF8") means that any string passed to/from V4REV will be
> UTF8 encoded. Nothing more. In theory you could use any encoding here.
> But due to the current Rev. unicode implementation, I think, it would be
> UTF8 only.
> 
> 2. Internally,  V4REV  uses  UTF16.
> 3. But  database could be saved as UTF16 encoding (implemented) so UTF8
>    one (not implemented yet).

Ron,

On disk Valentina keep info in UTF16.
And engine itself work in UTF16.

When you send V4RB UTF8 string then engine convert it into UTF16, then use.

Problem is that Revolution is not able handle UTF16 strings for now


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