Unicode is not "everywhere"...

Paul Dupuis paul at researchware.com
Thu Aug 22 16:17:26 EDT 2019


On 8/22/2019 4:08 PM, Richard Gaskin via use-livecode wrote:
> Dar Scott wrote:
>
> > If the result of shell() is run through textDecode, should then
> > shell() return binary data? This puts it outside the scope of
> > "everywhere". I like the idea, as long as simple ASCII characters
> > work transparently.
>
> Isn't that the goal of UTF-8, which is why so many programming 
> languages uses it as the default?
>

Richard is correct. UTF8 encoding does not change readability of ASCII 
characters.
Encoding the results from shell as UTF8 does mean that ASCII characters 
can be used in a return values without text decoding. shell() under OSX, 
at least tested under LC905rc1, actually returns UTF8 and probably no 
one using shell on OSX has noticed if you've just been working with 
ASCII characters as the output of your shell comamnd.





More information about the Use-livecode mailing list