On Mar 29, 2017, at 2:48 PM, The Tick <[email protected]> wrote:
>
> On 3/29/2017 3:25 PM, Warren Young wrote:
>>
>> Any text editor or compiler that can’t cope with UTF-8 in 2017 is broken or
>> can be ignored.
>
> I've been using vi for 40 years so that's not going to change.
I’ve “only” been using vi for about 37 years, and I can type UTF-8 in my vi
variant of choice just fine. (Vim, which got Unicode support in 2001.)
> I certainly won't revert to something as horrendous as notepad or similar.
Ironically, Notepad does support Unicode, completely, even UTF-8:
https://imgur.com/a/AIFZA
You know it’s time to update when your text editor of choice is outdone by
Notepad. :)
And no, I’m not endorsing Notepad. One of the things on my long to-do list is
a comparison of Windows 10 Notepad vs 1980 vi. Even the Unicode issue aside, I
think vi still wins, which is very sad.
>> It may be that your particular Tcl implementation is blindly assuming UTF-16
>> because you’re running it on Windows.
>
> Active State Tcl 8.6.4.
So bug ActiveState. Stock Tcl does the right thing.
> As much as I wish unix had supplanted windows, it's an unfortunate de facto
> standard for probably most people using desktop computers.
…or use WSL, or Cygwin.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
