V4RB, Jon, project

[Ruslan Zasukhin]

On 9/15/04 2:32 AM, "jda" <jda at his.com> wrote:

>>>  Any reason, in principle, that we can't mix encodings in a single
>>>  database -- use UTF-18 for VStrings and UTF-8 for VText. Does this
>>>  have to be database-wide -- can't it be field-specific, like language
>>>  is now?
>>> 
>>>  Anyway, if you are saying this as a warning, but we can still use
>>>  UTF-8 if we want, then point taken, and thanks.
>> 
>> Yes, you can use it.
>> 
>> Just we warn you that in this case user may get bad surprise that he can
>> store less chars.
>> 
> 
> Understood.
> 
> But what about the question -- would it be possible to define
> encoding on an individual field level? That would solve the problem.
> That's how language is assigned now...

Yes!

You can see this right now in the my example Common/Locale


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