Text encoding.

Mark Waddingham mark at livecode.com
Thu Sep 2 13:40:55 EDT 2021

On 2021-09-02 18:34, Mark Waddingham via use-livecode wrote:
> The character itself is the 'undefined/illegal codepoint' which has a
> different sequence of bytes for each of the main
> (UTF-8/16LE,BE/32LE,BE) encodings. If you do `hexdump -c | less` on
> the file, then if it is UTF-8 there will be three bytes before the T,
> or 4 if it is UTF-16.

Correcting myself - 4 if it is UTF-32 (which is exceptionally unlikely); 
2 if it is UTF-16.

Warmest Regards,


Mark Waddingham ~ mark at livecode.com ~ http://www.livecode.com/
LiveCode: Everyone can create apps

More information about the use-livecode mailing list