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.
UTF8 support in Windows is the major issue. Adding support by simply converting UTF8 to UTF16 just as it's done with ASCII will solve a lot problems working with WindowsAdetula supported this idea ·