Re: Unicode mysteries

I have filed a bug report bug_22561 re the misreporting of codepoints for unicode characters. I am pretty convinced the treatment of the Rainbow flag emoji as three separate characters should be treated as incorrect behaviour and therefore

Re: Unicode mysteries

> >> Which should correspond to codepoints >> 1F3F4 E0067 E0062 E0073 E0063 E0074 E007F >> And indeed if I manually build a UTF-16 string with these code points >> it does display as the flag of Scotland. So the lesson is that the >> reported chunks are not to be naively trusted --- tho

Re: Unicode mysteries

I see the flag here. Bob S On Mar 25, 2020, at 11:53 PM, Neville Smythe via use-livecode mailto:use-livecode@lists.runrev.com>> wrote: Taking a look at the Emoji ‘flag of Scotland’ character gbsct which won’t display here but exists in the Apple Color Emoji font and in corresponding fonts

Re: Unicode mysteries

On 2020-03-26 06:53, Neville Smythe via use-livecode wrote: Which should correspond to codepoints 1F3F4 E0067 E0062 E0073 E0063 E0074 E007F And indeed if I manually build a UTF-16 string with these code points it does display as the flag of Scotland. So the lesson is that the reported

Unicode mysteries

I am trying to understand the mysteries of unicode encodings; the following may (or may not) be useful (or confusing) to others. The docs say the full chunk expression for a unicode character is byte i of codeunit j of codepoint k of character c of str (with the warning that this is 'not