[V4REV] FIXED issue with umlauts and IOEncodiong.

Ruslan Zasukhin ruslan at paradigmasoft.com
Thu Jul 29 14:05:46 CDT 2010


On 7/29/10 11:45 AM, "Mark Schonewille" <m.schonewille at economy-x-talk.com>
wrote:

> I also include a slightly modified version of my sample stack. It
> appears that the default is no longer Macintosh (on Mac OS X systems)
> but something that resembled UTF16.

Exactly. I think it is
     UT16 Big Endian

> As long as I call the IOEncoding
> function explicitly before running the script in my sample stack, all
> works fine. 

Right.

I also have add in your stack you have sent me few days ago

    Database_Open()
    Database_IOEncoding( dbRef ,  "Macintosh" )

> I don't know whether you meant to mention this on your
> blog, but I didn't see it or didn't understand it. The instructions
> given on your blog are clear, except that IOEncoding needs to be
> called always.

Yes always after db open or db create

This becomes clear if you remember that you can also connect to VSERVER.

So you connect, open db, and then you PROMISE / ASK
That your INPUT and OUTPUT strings will be in THIS encoding.

But other users of that VSERVER may want work with OTHER encoding.

So VSERVER on the fly convert for each user to asked encoding

Cool?  :-)


> Many thanks again!

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




More information about the Valentina mailing list