Thanks. I appreciate your commitment to quality and look forward to Field
Trip.
-- Tom Bodine
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/FT-Another-FieldTrip-Pre-Beta-Note-tp4658105p4658128.html
Sent from the Revolution - User mailing list archive at Nabble.
Thanks for this short list news report Curry !
Best,
Pierre
Le 14 déc. 2012 à 15:09, Curry Kenworthy a écrit :
>
> Howdy FieldTrip Folks,
>
> While testing and wrapping up this first version of FT, I decided to add a
> few more features, and also ran into a crasher LC field bug on Android to
There is a discussion with algorithms here:
http://www.unicode.org/faq/utf_bom.html#utf16-4
However, I cannot understand it, and feel that there is an element of
obfuscation going on there.
Richmond.
___
use-livecode mailing list
use-livecode@lists.r
On 12/15/2012 04:40 PM, Peter W A Wood wrote:
Richmond
Maybe this is a bit naive; but how does one derive the 2 Hex numbers for a
character beyond the
Basic Multilingual Plane if one knows the Unicode address?
The algorithm is explained here -
http://en.wikipedia.org/wiki/UTF-16#Code_points_
Richmond
> Maybe this is a bit naive; but how does one derive the 2 Hex numbers for a
> character beyond the
> Basic Multilingual Plane if one knows the Unicode address?
The algorithm is explained here -
http://en.wikipedia.org/wiki/UTF-16#Code_points_U.2B1_to_U.2B10
Implementing it wi
On 12/13/2012 04:29 AM, Peter W A Wood wrote:
According to the User Guide, LiveCode employs UTF-16 encoding:
"LiveCode fields and other controls use the UTF-16 encoding for Unicode. In order to use
Unicode in a field or in the labels of controls, paste in Unicode text, or set the textFont of th
