Char Set on Custom Properties

Mark Schonewille m.schonewille at economy-x-talk.com
Wed Jul 22 23:13:29 CEST 2015


Hi Dan,

Not exactly. All text is now unicode. If you set a custom property to 
the text of a field, it is unicode already. When you set the text of a 
field to a property, it is again unicode. This avoids the need for 
mapping and other hacks.

I haven't tested this much. I can imagine that this is confusing, 
particularly if you work with stacks on both old and new formats. If you 
only use the new format, however, it is very convenient and you will 
quickly get used to it.

--
Best regards,

Mark Schonewille

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

Installer Maker for LiveCode:
http://qery.us/468

Buy my new book "Programming LiveCode for the Real Beginner" 
http://qery.us/3fi

LiveCode on Facebook:
https://www.facebook.com/groups/runrev/

On 7/22/2015 23:06, Dan Friedman wrote:
> Hello!   Way back in LiveCode 5 and 6, custom properties were not ported to the proper character set when you opened the stack on a different platform (Mac --> Win or Win --> Mac).  This was easily solved by a simple macToISO() or ISOtoMac().   However, it appears that LC 7.x is now doing this char mapping for custom properties on it's own.  Before I modify a mountain of code, can anyone confirm that LC 7+ automatically maps custom properties to the proper char set for the host platform?
>
> Thanks!
> Dan




More information about the use-livecode mailing list