Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Output and terminal windows charset problem #267

Closed
xzzh999 opened this issue Nov 29, 2017 · 7 comments
Closed

Output and terminal windows charset problem #267

xzzh999 opened this issue Nov 29, 2017 · 7 comments
Labels
bug a bug in the product duplicate a duplicate of an already present issue
Milestone

Comments

@xzzh999
Copy link

xzzh999 commented Nov 29, 2017

Hi, bigcow! Great work!

When i build msvc c++ project, the output window always print garbled,
i tried follow issue's suggestion but they were complicated and didn't work.

microsoft/vscode#3550

dotnet/vscode-csharp#1775

can you add some charset encoding settings to make this easy?

@xzzh999
Copy link
Author

xzzh999 commented Nov 29, 2017

vscode version: 1.18.1, shell: 1.7.9, node: 7.9.0

@vector-of-bool
Copy link
Contributor

I've had a few troubles with character encoding. This is on the backlog.

@vector-of-bool vector-of-bool added this to the Backlog milestone Nov 30, 2017
@vector-of-bool vector-of-bool added the bug a bug in the product label Nov 30, 2017
@feng-ye
Copy link

feng-ye commented Dec 4, 2017

I am using the following work around:

  1. create a bat file containing
    chcp 65001 && cmake %*
  2. set cmake.cmakePath to the bat file

I hope this will help.

@xzzh999
Copy link
Author

xzzh999 commented Dec 8, 2017

For now i wrote some python scripts to generate and build the project myself, and every charset encoding is under control in vscode, but i hope this extension will improved later, then i will change back.

@eternalphane
Copy link

Maybe you can temporary patch it by adding an option in settings.json to let user manually set their preferred output encoding, and provide a permanent solution later.

@pengbins
Copy link
Contributor

pengbins commented Sep 19, 2018

I am using the following work around:

  1. create a bat file containing
    chcp 65001 && cmake %*
  2. set cmake.cmakePath to the bat file

I hope this will help.

@feng-ye I tried your work around, but got following error. It seems .bat can't run.
[rollbar] Unhandled exception: Unhandled Promise rejection: build Error: Impossible: CMake driver died immediately after successful configure {}

@bobbrow bobbrow added the duplicate a duplicate of an already present issue label Jul 24, 2019
@bobbrow
Copy link
Member

bobbrow commented Jul 24, 2019

This looks like a duplicate of #153 which may have been fixed by PR #550. Is this still an issue for you?

@bobbrow bobbrow closed this as completed Jul 24, 2019
@github-actions github-actions bot locked and limited conversation to collaborators Feb 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug a bug in the product duplicate a duplicate of an already present issue
Projects
None yet
Development

No branches or pull requests

6 participants