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. Here is what utf16le.txt (from Fossil test directory) looks like to me: \xff\xfeT^@h^@i^@s^@ ^@f^@i^@l^@e^@ ^@c^@o^@n^@t^@a^@i^@n^@s^@ ^@u^@t^@f^@-^@1^@ 6^@l^@e^@ ^@t^@e^@x^@t^@.^@ Usually when I see a file like this, I just do: tr -d \\000 < utf16le.txt > newutf16le.txt Then I remove any BOM that might exist because who needs it? Now I see: This file contains utf-16le text. Do I need UTF-8? Not really. I don't even have a keyboard that can produce any UTF-8 characters; except those which overlap with ASCII, and even then, they are only 1 byte characters anyway. You can claim that nvi is broken or can be ignored, but I still use it, and don't see a good reason to stop using it (UTF-8 support is not high on my list of reasons to change to a new editor). I cannot stand vim. Maybe one day nvi will have UTF-8 support, but I'm not counting on it any time soon. :-) Andy -- TAI64 timestamp: 4000000058dc738a _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
