Read on Twitter
Thinking of starting a series about "How Windows locales work" and each article is just "they don& #39;t", "they really don& #39;t" and "you don& #39;t want to know"
Up until today I was lulled into a false sense of security by the advice "just use the W functions, never the A functions" until I saw this happen on the same computer.
(left is MSYS2, right is Powershell)
(left is MSYS2, right is Powershell)
"Okay so msys2 sucks" not quite, because... it *does* let me echo random UTF-8 stuff, no problem.
And of course, *of course* if you use "chcp" to change the current codepage from 437 to 65001, it "works". Although that breaks a lot of other programs, I hear.
And of course, *of course* if you use "chcp" to change the current codepage from 437 to 65001, it "works". Although that breaks a lot of other programs, I hear.
"Okay so msys2 does suck" well here& #39;s the output of a similar program on my *other* Windows computer:
They both have the same "WinSystemLocale" btw
They both have the same "WinSystemLocale" btw
Let& #39;s check the windows locale settings which are *not* in the Win10 settings thing, they are in `Control Panel (1)`
*neither computer* has "Beta: Use Unicode UTF-8 for worldwide language support" enabled
*neither computer* has "Beta: Use Unicode UTF-8 for worldwide language support" enabled
Twist ending: it appears MSYS2 (or rather, Cygwin) *did* mess with something but there& #39;s currently only one person in the issue tracker who claims to be affected.
Starting to think there& #39;s a conspiracy out there, now I need to figure out what links github user "nyfair" and me..
Starting to think there& #39;s a conspiracy out there, now I need to figure out what links github user "nyfair" and me..
Reading Cygwin 3.1 changes, it appears Windows 10 1809 added "console APIs on virtual terminal" which I& #39;m assuming means "winpty.exe" should no longer be needed?
but also yeah stuff& #39;s broken for now.
but also yeah stuff& #39;s broken for now.
This is not even a (good) rant thread because there& #39;s no villain here.
MS is incrementally adding UTF-8 support while preserving backwards compat. Cygwin is trying to expose new features. MSYS2 packages are kept up-to-date (and there& #39;s a zillion of them).
It& #39;s just a Day.
MS is incrementally adding UTF-8 support while preserving backwards compat. Cygwin is trying to expose new features. MSYS2 packages are kept up-to-date (and there& #39;s a zillion of them).
It& #39;s just a Day.
Here& #39;s a wonderful screenshot to end this thread:
