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

Switching Windows Terminal Language #7040

Closed
espresso3389 opened this issue Jul 23, 2020 · 2 comments
Closed

Switching Windows Terminal Language #7040

espresso3389 opened this issue Jul 23, 2020 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@espresso3389
Copy link

Description of the new feature/enhancement

We need some settings.json setting to change localization of Windows Terminal GUI.

Sometimes localization may break certain functionality and we want to turn off localization (back to plain English mode).

For me, #7039 is a critical issue and want to disable Japanese localization somehow...

@espresso3389 espresso3389 added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jul 23, 2020
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jul 23, 2020
@DHowett
Copy link
Member

DHowett commented Jul 27, 2020

Thanks for the request (and reporting the command palette localization issue!). We're tracking this in /dup #5497

@ghost
Copy link

ghost commented Jul 27, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Jul 27, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jul 27, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants