Droid issues - Legacy Bash IFS var clobbering VLIW offset?

[Stewart C. Russell]

On 11-11-25 04:24 , Walter Dnes wrote:
>
>    UTF8 is getting beyond plain text.  You could be doing Chinese,
> Japanese or Sanskrit in UTF8.

Well, that's good news for the more than half of the world that isn't 
adequately represented by ASCII.

>  Also, what do you really accomplish by
> using...

They're the proper characters to use. The typewriter, then teletype, 
then ASCII, have a lot of wrongs to answer for. Two spaces after a 
period, f'rinstance …

> Way back when, "plain text" was implicitly assumed to be ASCII.

Wayer backer whener, it could've been Baudot. I mean, who really needs 
more than five bits in a character set? Lower case is greatly overrated. 
If that's not plain enough, we should use Morse - and none of that wispy 
post-1859 International Morse, either, but the one that Samuel hath wrought.

> Now, with the advent
> of UTF8, we may have to explicitly say ASCII, rather than merely saying
> "No HTML".

You might not want to do that. Firstly, it's retrograde. Secondly, you 
can't properly represent names written in one of the official languages 
of Canada in ASCII, and there's this Charter thing.

  Stewart
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists