Richmond
I wouldn't be surprised to find that the second char of FFF contains 56833. In
fact that is what I would expect with UTF-16 encoding. (Sorry that I can't
check at the moment).
Regards
Peter
On 15 Jan 2014, at 17:38, Richmond wrote:
> On 15/01/14 10:03, Peter W A Wood wrote:
>> Richm
On 15/01/14 11:46, J. Landman Gay wrote:
On my Android tablet using, I assume, Droid Sans, the clef sign was missing but
the pile of poo was there. To me it looked more like a party hat with yellow
streamers, but admittedly the font was small.
Presumably you meant to type "f*rty hat".
Richm
On my Android tablet using, I assume, Droid Sans, the clef sign was missing but
the pile of poo was there. To me it looked more like a party hat with yellow
streamers, but admittedly the font was small.
Richmond wrote:
>On 15/01/14 10:03, Peter W A Wood wrote:
>> Richmond
>>
>> Apparently th
On 15/01/14 10:03, Peter W A Wood wrote:
Richmond
Apparently the "Grinning Face" is included in the Deja Vu font which was/is
included by default with Ubuntu (according to Wikipedia). Perhaps you can get LiveCode to
use that ... at least to test the surrogate pairs.
On a lesser note, LibreOff
On 15/01/14 10:03, Peter W A Wood wrote:
Richmond
Apparently the "Grinning Face" is included in the Deja Vu font which was/is
included by default with Ubuntu (according to Wikipedia). Perhaps you can get LiveCode to
use that ... at least to test the surrogate pairs.
On a lesser note, LibreOff
Richmond
Apparently the "Grinning Face" is included in the Deja Vu font which was/is
included by default with Ubuntu (according to Wikipedia). Perhaps you can get
LiveCode to use that ... at least to test the surrogate pairs.
On a lesser note, LibreOffice includes Deja Vu and fortunately Deja V
On 15/01/14 02:55, Peter W A Wood wrote:
Richmond
Have you tried displaying the pile of poo in LivecCode using the same font as
you are using in Thunderbird? That would be the best evidence of whether
LiveCode supports surrogate pairs under Linux or not.
Regards
Peter
That's a godd idea;
info/unicode/char/1F600/index.htm
>>>>
>>>> and this is the unusual character:
>>>> http://www.fileformat.info/info/unicode/char/1F4A9/index.htm
>>>>
>>>>
>>>> Thanks, Alejandro,
>>> The "problem" is that
volution.278305.n4.nabble.com/numToChar-with-socking-great-numbers-tp4674643p4674681.html
Sent from the Revolution - User mailing list archive at Nabble.com.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe,
and this is the unusual character:
http://www.fileformat.info/info/unicode/char/1F4A9/index.htm
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/numToChar-with-socking-great-numbers-tp4674643p4674681.html
Sent from the Revolution - User mailing list archi
--
View this message in context: http://runtime-revolution.
278305.n4.nabble.com/numToChar-with-socking-great-
numbers-tp4674643p4674681.html
Sent from the Revolution - User mailing list archive at Nabble.com.
___
use-livecode mailing list
use-live
-pair system doesn't seem to work
> properly.
>
>
> Richmond.
>
>
>
>>
>>
>>
>> --
>> View this message in context: http://runtime-revolution.
>> 278305.n4.nabble.com/numToChar-with-socking-great-
>> numbers-tp4674643p4674681.ht
is that I would like to be able to display the first, and
any other astral plane Unicode
character in Livecode, and the surrogate-pair system doesn't seem to
work properly.
Richmond.
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/numToChar-wit
/numToChar-with-socking-great-numbers-tp4674643p4674681.html
Sent from the Revolution - User mailing list archive at Nabble.com.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
On 13/01/14 16:39, Fraser Gordon wrote:
Hi Phil,
We do intend to have RTL support in the 7.x cycle. What is most likely to happen is that
we'll initially introduce a simplified mode where a field is exclusively right-to-left or
left-to-right and mixing isn't really supported. (Individual words
On 13/01/14 16:39, Fraser Gordon wrote:
Hi Phil,
We do intend to have RTL support in the 7.x cycle. What is most likely to happen is that
we'll initially introduce a simplified mode where a field is exclusively right-to-left or
left-to-right and mixing isn't really supported. (Individual words
That’s really exciting news; it’s long overdue but still exciting.
But I don’t think the users {we, programmers} will complain much about
bidirectional support.
Even the biggest services don’t give full support to bidirectional text.
I remember that I once published a short fairy-tale of mine to
Thanks Fraser! I am waiting with bated breath!
Phil
On 1/13/14, 6:39 AM, Fraser Gordon wrote:
Hi Phil,
We do intend to have RTL support in the 7.x cycle. What is most likely to happen is that
we'll initially introduce a simplified mode where a field is exclusively right-to-left or
left-to-r
Hi Phil,
We do intend to have RTL support in the 7.x cycle. What is most likely to
happen is that we'll initially introduce a simplified mode where a field is
exclusively right-to-left or left-to-right and mixing isn't really supported.
(Individual words in a mixed setting should render in the
Regarding 7.0 and Unicode... Is it possible that we'll see support for
RTL text in 7.0? Or maybe 7.x?
Thanks -
Phil Davis
On 1/13/14, 2:24 AM, Fraser Gordon wrote:
Hi Richmond,
My bad, should have been:
numtoChar(55357) & numToChar(56832)
Note that current versions of LiveCode don't really
On Linux I get a single empty box. I suspect that the emoji aren't really that
widely supported outside relatively recent OSX systems. (It works fine on OSX
10.8).
On 13 Jan 2014, at 10:43, Richmond wrote:
> On 13/01/14 12:24, Fraser Gordon wrote:
>
> Well, the scriptEditor didn't throw a blu
On 13/01/14 12:24, Fraser Gordon wrote:
Hi Richmond,
My bad, should have been:
numtoChar(55357) & numToChar(56832)
Note that current versions of LiveCode don't really treat surrogate pairs
properly - each codeunit of the pair is treated as a character so it is
possible to do things like appl
2014/1/13 Richmond :
>set the useUnicode to true
>set the unicodetext of fld "" to numtoChar(55357) + numToChar(56832)
>
> and got this:
>
> button "Button": execution error at line 3 (Operators +: error in left
> operand), char 56
Replacing + by & , will this please you ?
Thierry
Hi Richmond,
My bad, should have been:
numtoChar(55357) & numToChar(56832)
Note that current versions of LiveCode don't really treat surrogate pairs
properly - each codeunit of the pair is treated as a character so it is
possible to do things like apply a style that only affects one of the two
On 13/01/14 01:43, Fraser Gordon wrote:
You need two numToChar calls:
numToChar(55357)+ numToChar(56832)
The Unicode engine will fix this with a new call that handles surrogate
pairs automatically and invisibly but numToChar will probably have to
retain the mod-65536 behaviour for compatibility
On 13/01/14 01:43, Fraser Gordon wrote:
You need two numToChar calls:
numToChar(55357)+ numToChar(56832)
The Unicode engine will fix this with a new call that handles surrogate
pairs automatically and invisibly but numToChar will probably have to
retain the mod-65536 behaviour for compatibility
You need two numToChar calls:
numToChar(55357)+ numToChar(56832)
The Unicode engine will fix this with a new call that handles surrogate
pairs automatically and invisibly but numToChar will probably have to
retain the mod-65536 behaviour for compatibility.
Regards,
Fraser
On 12/01/2014 21:31, R
On 12/01/14 23:31, Richmond wrote:
So, I found that the Unicode Consortium puts a smiley face at address
1F600 (hex) = 128512(decimal),
but when I go
set the useUnicode to true
set the unicodeText of fld "feeld" to numToChar(128512)
I get a nifty Bengali char that returns 62976, which is, rat
So, I found that the Unicode Consortium puts a smiley face at address
1F600 (hex) = 128512(decimal),
but when I go
set the useUnicode to true
set the unicodeText of fld "feeld" to numToChar(128512)
I get a nifty Bengali char that returns 62976, which is, rather predictably,
128512 - 65536 (or
29 matches
Mail list logo