Encoding of 1-2 converted db

[Ruslan Zasukhin]

On 10/16/05 11:34 AM, "Leo Van den Brande" <leo_van_den_brande at wxs.nl>
wrote:

>> I filed a bug report on this a long time ago (can't find it on Mantis
>> right now). Ruslan says that's because V2 doesn't know the encoding
>> of the source 1.x db. I pointed out that if the specified language is
>> a Roman one (like English) the encoding will be MacRoman on a Mac,
>> and so the conversion should work. That was the end of it. I think
>> all conversion-related issues have been tabled...
> 
> I used encoding MacRoman for Mac build and WindowsLatin1 for Windows both for
> storage and retrieval.
> The v1 db which I am presently trying to convert was created on a Mac build.
> However, I should also be able to convert v1 db's which have been created and
> filled by the users running a Windows build.

Leo,

Well it looks we need with your help try resolve this problem.

So we will need

* detailed description of
    - what you have
    - what you do
    - what you get
    - what you expect to get

* some small dbs for us to test


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