Umlaute get corrupted when transfering livecode from Win to Mac

Mark Schonewille m.schonewille at economy-x-talk.com
Tue May 8 07:06:25 EDT 2012


Hi Tiemo,

I have seen this problem in two different cases. I don't know the cause and have no solution but you could check the charSet property of the stack when you open the stack. If you move the stack from Mac to Windows and the charSet property returns ISO before you save the stack for the first time on the Windows machine, then something must have gone wrong. If you move the stack from Windows to Mac and the charSet property returns MacOS before you save the stack for the first time on the Mac, then something must have gone wrong as well. Perhaps keeping an eye on the value returned by this property will eventually give you some insights into this problem. I'm saying "perhaps", because I this happens too sporadically to actually check whether my assumptions are true.

--
Best regards,

Mark Schonewille

Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK: 50277553

We will have room for new projects after 1 June. Contact me now and be first in line.

On 8 mei 2012, at 12:16, Tiemo Hollmann TB wrote:

> Hello,
> 
> from time to time german Umlaute in livecode files get corrupted when
> transferring the files between the platforms Win <-> Mac. My development is
> primary on Win, but testing and building the standalone I do on each
> platform. But I tried it also the other way
> 
> This happens irregulary and not reproduceable. To me it happened in the
> standalone setting, e.g. name of application, as well as in the scripts,
> which can lead to corrupted scripts. I try to avoid umlaute in handler or
> variable names, but can't avoid them always in object names, messages,
> labels, titles, etc.
> 
> Did anybody else encountered this? Any ideas how to avoid, to check for?
> 
> Tiemo
> 





More information about the use-livecode mailing list