Prev: Digital Signature
Next: Importing fullblown 3D scenes: Only possible viaShockwave 3D .w3d format ?
From: alchemist on 16 Jul 2008 10:43
Download:
http://xtrema.rtr.gr/beta/xtrema.rar

I believe that the codepage you should use is 1252. if not, check
http://www.microsoft.com/globaldev/reference/WinCP.mspx for the proper code.
Assuming the string you get from ado is adoStr, use:

uniStr= _aa(adoStr, 1252).dirstring
or
uniStr= _aa(adoStr).dirstring -- this will use your system's code page.

_aa() will perform a raw import of director string adoStr (ansi from ansi),
and .dirstring
will return a director string according to the dir version (ansi, or utf8
for
dir11).
To check if the import will work as expected, you can try:
_aa(adoStr,1252).pop()

To update the database to utf8 format, you can read all entries and replace
them with the converted strings.

You could also use the xtra's xCom object to access your database, which can
easilly handle such issues and supports all vb data types - just that it's
not documented yet. It soon will be though.

Let me know if the above works for you.


"Locknar" <no_gracias(a)paso.com> wrote in message
news:g5ktk7$kff$1(a)forums.macromedia.com...
> Could you suggest me any solution? Any other Xtra or so.
>
> Thanks Mike.
>
> "Mike Blaustein" <mblaustein(a)gmail.com> escribi� en el mensaje de noticias
> news:g5krte$ikc$1(a)forums.macromedia.com...
>> Since ADOxtra has not been updated to use Director 11, it can not handle
>> Unicode characters. The accented characters will be unavailable in
>> Director 11 until the author of the xtra makes a new compatible
>> version... if they ever release a Director 11 version...
>



From: alchemist on 16 Jul 2008 13:19
Great to hear this, Locknar!
Far as the nickname is concerned though, it comes from when I often had to
resort to awkward methods to deal with director quirks. Now it's all
about solutions, not workarounds, so perhaps I should reconsider ;-).


"Locknar" <no_gracias(a)paso.com> wrote in message
news:g5l91n$3j4$1(a)forums.macromedia.com...
> ������� IT WORKS !!!!!!!
>
> I've used the 1252 codepage and works perfectly.
> Now I understand your nick name.
>
> Thank you very much "alchemist"
>
>
> "alchemist" <unknown(a)domain.com> escribi� en el mensaje de noticias
> news:g5l1el$on1$1(a)forums.macromedia.com...
>> Download:
>> http://xtrema.rtr.gr/beta/xtrema.rar
>>
>> I believe that the codepage you should use is 1252. if not, check
>> http://www.microsoft.com/globaldev/reference/WinCP.mspx for the proper
>> code.
>> Assuming the string you get from ado is adoStr, use:
>>
>> uniStr= _aa(adoStr, 1252).dirstring
>> or
>> uniStr= _aa(adoStr).dirstring -- this will use your system's code page.
>>
>> _aa() will perform a raw import of director string adoStr (ansi from
>> ansi), and .dirstring
>> will return a director string according to the dir version (ansi, or utf8
>> for
>> dir11).
>> To check if the import will work as expected, you can try:
>> _aa(adoStr,1252).pop()
>>
>> To update the database to utf8 format, you can read all entries and
>> replace
>> them with the converted strings.
>>
>> You could also use the xtra's xCom object to access your database, which
>> can
>> easilly handle such issues and supports all vb data types - just that
>> it's
>> not documented yet. It soon will be though.
>>
>> Let me know if the above works for you.
>>
>>
>> "Locknar" <no_gracias(a)paso.com> wrote in message
>> news:g5ktk7$kff$1(a)forums.macromedia.com...
>>> Could you suggest me any solution? Any other Xtra or so.
>>>
>>> Thanks Mike.
>>>
>>> "Mike Blaustein" <mblaustein(a)gmail.com> escribi� en el mensaje de
>>> noticias
>>> news:g5krte$ikc$1(a)forums.macromedia.com...
>>>> Since ADOxtra has not been updated to use Director 11, it can not
>>>> handle
>>>> Unicode characters. The accented characters will be unavailable in
>>>> Director 11 until the author of the xtra makes a new compatible
>>>> version... if they ever release a Director 11 version...
>>>
>>
>>
>>
>



From: alchemist on 16 Jul 2008 13:30
> It's really annoying.
You understand that the version you are using is a beta, and should not be
used in release products, right?
You can perform the required conversions, update your existing database, and
then stop using it. If you don't call any commands, the debugger won't
appear.
Case you want to try some of it's features though: xDebuggerEnabled(0)
I wonder how you could do that without the docs, though..
The ones on the site refer to older versions of the xtra, and the new ones
won't be released till next week.

"Locknar" <no_gracias(a)paso.com> wrote in message
news:g5la63$4n6$1(a)forums.macromedia.com...
> Could you tell me how can I avoid the debug window who appears when you
> execute and exit the program?
> It's really annoying.
> Thanks.
>
> "alchemist" <unknown(a)domain.com> escribi� en el mensaje de noticias
> news:g5l1el$on1$1(a)forums.macromedia.com...
>> Download:
>> http://xtrema.rtr.gr/beta/xtrema.rar
>>
>> I believe that the codepage you should use is 1252. if not, check
>> http://www.microsoft.com/globaldev/reference/WinCP.mspx for the proper
>> code.
>> Assuming the string you get from ado is adoStr, use:
>>
>> uniStr= _aa(adoStr, 1252).dirstring
>> or
>> uniStr= _aa(adoStr).dirstring -- this will use your system's code page.
>>
>> _aa() will perform a raw import of director string adoStr (ansi from
>> ansi), and .dirstring
>> will return a director string according to the dir version (ansi, or utf8
>> for
>> dir11).
>> To check if the import will work as expected, you can try:
>> _aa(adoStr,1252).pop()
>>
>> To update the database to utf8 format, you can read all entries and
>> replace
>> them with the converted strings.
>>
>> You could also use the xtra's xCom object to access your database, which
>> can
>> easilly handle such issues and supports all vb data types - just that
>> it's
>> not documented yet. It soon will be though.
>>
>> Let me know if the above works for you.
>>
>>
>> "Locknar" <no_gracias(a)paso.com> wrote in message
>> news:g5ktk7$kff$1(a)forums.macromedia.com...
>>> Could you suggest me any solution? Any other Xtra or so.
>>>
>>> Thanks Mike.
>>>
>>> "Mike Blaustein" <mblaustein(a)gmail.com> escribi� en el mensaje de
>>> noticias
>>> news:g5krte$ikc$1(a)forums.macromedia.com...
>>>> Since ADOxtra has not been updated to use Director 11, it can not
>>>> handle
>>>> Unicode characters. The accented characters will be unavailable in
>>>> Director 11 until the author of the xtra makes a new compatible
>>>> version... if they ever release a Director 11 version...
>>>
>>
>>
>>
>



 | 
Pages: 1
Prev: Digital Signature
Next: Importing fullblown 3D scenes: Only possible viaShockwave 3D .w3d format ?