744 votes21 comments · Command Prompt / Console / Windows Subsystem for Linux (WSL) » Console/Terminal · Flag idea as inappropriate… · Admin →
As Chip said, UTF-16 is rather baked into the stuff we do. The console host does use UTF-16 somewhere in there. :P We just have the matter of dealing with code pages throughout the history of computing existence that causes us heartburn every time we think about how to fix this. :( It’s definitely something that we would like to look into on our backlog.
—MichaelShunichi Arai commented
I'm a Japanese Ruby developer using Windows environment. Currently I have a huge pain that the cmd.exe supports only SJIS encoding, also its support for Japanese input method is quite horrible. I wish a good multilingual support with Bash in Windows.Shunichi Arai supported this idea ·