Showing Chinese Mojibake in new version 1.7.1
See original GitHub issueBrief Issue Summary
Can’t display Chinese properly in the terminal window in the new version 1.70+
Expected:
Showing Chinese like "生成“
Apparent Behavior:
Showing Mojibake like “???”
CMake Tools Log
<!-- Paste the log contents HERE -->
Developer Tools Log
<!-- Paste the log contents HERE -->
Platform and Versions
- Operating System: Windows 10 20H2
- CMake Version: 3.20.0
- VSCode Version: 1.55.2
- CMake Tools Extension Version: 1.7.1
- Compiler/Toolchain: VS 2019
Other Notes/Information
Downgrade to 1.6.0 can resolve this issue
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Why does misdetected Unicode text tend to show up as ...
Why does misdetected Unicode text tend to show up as Chinese characters? ... Why does ASCII→Unicode mojibake result in Chinese?
Read more >Changelog - Sphinx documentation
Support docutils-0.17. Please notice it changes the output of HTML builder. Some themes do not support it, and you need to update your...
Read more >can't show chinese character #6212 - spyder-ide ... - GitHub
can't show chinese character #6212 ... Version and main components. Spyder Version: 4.0.0.dev0 0608076; Python Version: 2.7.12; Qt Versions: ...
Read more >Basics of Chinese Writing (Hanzi) Part 1/3 - YouTube
Have you ever wanted to read or write Chinese characters, but felt absolutely overwhelmed? In this series of videos, we break Chinese ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@LoSealL, can you test the vsix here (https://github.com/microsoft/vscode-cmake-tools/actions/runs/811030625) and let us know if it fixes the problem? This fix will be included in 1.7.2 which will be released later this week but we are not sure if it addresses your scenario or not.
Excellent, thank you for confirming.