Sure, but if you have to correct a field using isoToMac and macToIso
every time your stack opens, you might as well just replace the ASCII 16
value with ≤ in the HTML text of the field. I think Graham's point is
that this shouldn't be necessary and I believe in 7 it should indeed no
longer be necessary.
--
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 10/31/2014 20:03, J. Landman Gay wrote:
On 10/31/2014, 1:04 PM, Graham Samuel wrote:
Not to flog this to death, but what you did works for me too - you
just set the htmlText of a field using a version of LC running on
Windows. What didn’t work for me was setting the htmlText of the
field using a Mac version of LC, saving the stack and then opening it
on a PC with a PC version of LC - then the field had somehow changed.
I will see if this applies in other versions of LC. What I did is
repeatable but of course it may be something to do with my particular
setup or versions of LC.
That's what MacToISO and ISOtoMac were for. I'm not sure they still
apply in LC 7.0 though. But if you're running in 6.x you'll probably
need to use macToISO() on the text if the platform is a Windows machine.
Or, you could try storing the HTML as a custom property and re-setting
the htmlText on Windows; maybe that will map it correctly.
That said, if those particular characters aren't in the Windows
character set then I don't think anything will work to display them.
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
