On Mar 29, 2017, at 8:54 PM, Andy Bradford
<amb-sendok-1493434470.mmjmhcdkgpnhiioca...@bradfords.org> wrote:
>
> Thus said Warren Young on Wed, 29 Mar 2017 14:25:34 -0600:
>
>> Any text editor or compiler that can't cope with UTF-8 in 2017 is
>> broken or can be ignored.
>
> I rarely use any editor but nvi. It doesn't support UTF-8.
According to Wikipedia, nvi got Unicode support in 2000.
Here on my Mac, “brew install nvi” gets me an nvi that does preserve UTF-8
non-ASCII characters in files, and does let me insert them. It claims to be
version 1.81.6_3.
I did see one bobble in its handling of UTF-8, namely that I had to say ‘x’
twice to get it to delete a character that’s expressed as 2 bytes in UTF-8.
> Here is what
> utf16le.txt (from Fossil test directory) looks like to me:
That’s UTF-16, of course, so no surprise that nvi doesn’t do the right thing on
a machine that is likely using either a UTF-8 or ISO-8859 locale setting.
A more useful test would be the W3C’s UTF-8 test file:
https://www.w3.org/2001/06/utf-8-test/UTF-8-demo.html
And if that fails, what is your LANG/LC_* variable set to?
> Do I need UTF-8? Not really.
I don’t think it’s fair to notable Fossil users like Jörg Sonnenberger that we
misspell their names simply because we refuse to give up ASCII-centrism.
That was fine 15-20 years ago, when Unicode support on *ix platforms was still
weak, but the first Bubble exposed most of these problems to the Many Eyeballs.
> I don't even have a keyboard that can
> produce any UTF-8 characters
That’s purely a local issue. Many people do have such keyboards, as I’ve
demonstrated above. And I’m not German. Or Swedish. Or Dutch.
And that’s just the consequences of missing out on one single accent.
> except those which overlap with ASCII, and
> even then, they are only 1 byte characters anyway.
You must mean ISO-8859 or or one of the Windows code pages, not ASCII.
X3.4-1968 (the last version) is a 7-bit character set. When expressed with
8-bit code points, the meaning of values > 127 is not defined by ASCII.
And since ISO-8859 and the Windows code pages are all mutually incompatible
except for their shared ASCII subset, we need Unicode. We have lots of
solutions to parts of the problem, but only Unicode solves the whole problem.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
