strange char translation from intel to ppc

[Bernard Devlin]

Bonjour Eric,

I think the problem may be that I'm using these characters within the keys
of an array, then storing the array as a custompropertyset.  Whilst these
characters are not strictly alphanumeric, since they are ascii, I didn't
think there would be a problem.  But perhaps because they are not the
content of the array, there is still an isoToMac conversion going on.  And
since their numerical value is below 128, I think maybe they are being
mis-translated as per the bug I referenced.

For about 15 years of my life there was a very good chance that whenever I
drove a car it would stop working.  Friends and family used to take me along
when they were buying a car, and if it didn't break down whilst I did the
test drive they would buy it.  Then I seemed to lose this 'gift', and in the
last 10 years I never had a car break down on me.

I'm starting to think the planets have re-aligned themselves, and my 'gift'
has returned.  In the absence of a car, my 'gift' has found a new target.

Bernard

On Thu, Oct 9, 2008 at 8:50 AM, Eric Chatonet <
eric.chatonet at sosmartsoftware.com> wrote:

> Bonjour Bernard,
>
> When you open a stack created on Win with Mac OS, the engine converts all
> 'texts' (scripts, objects names, etc.) using IsoToMac function (and MacToIso
> when it's the opposite).
> There is only one thing that is never converted and stays 'untouched' when
> switching from a platform to another: custom properties.
> Because custom properties may contain binaries.
> So I don't understand...
> Best regards from Paris,
> Eric Chatonet.
> ----------------------------------------------------------------
> Plugins and tutorials for Revolution: http://www.sosmartsoftware.com/
> Email: eric.chatonet at sosmartsoftware.com/
> ----------------------------------------------------------------
>