V4RB

[Ruslan Zasukhin]

On 3/11/04 3:14 PM, "jda" <jda at his.com> wrote:

>>>  Or we need have special flag Default
>>>  Or always UTF8
>> 
>> I would say UTF-8 is great, but someone in Japan or so would eventually
>> say UTF-16. But if we can set it in every select or as default at
>> ValentinaOpen it would also be ok.
>> What do the others think about it?
>> 
> 
> Since RB's "native" encoding now is UTF-8, I think it makes sense to
> return it as that. I don't know why anyone would want to handle
> UTF-16 while "in" the app since at this point it's not about storage,
> UTF-8 handles Japanese just fine, and they would have to specifically
> set the encoding of string literals and editfield text to UTF-16
> whenver they used them. Even if they did (would anyone here want
> that?) using a TextConverter to change the text encoding would be
> easy.

I think we will start with UTF8,

If this will cause some problems for somebody then we improve this by
additional option.

-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------