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

Add something besides command line option to configure locale #4118

Closed
alexdima opened this issue Mar 14, 2016 · 5 comments
Closed

Add something besides command line option to configure locale #4118

alexdima opened this issue Mar 14, 2016 · 5 comments
Assignees
Labels
feature-request Request for new features or functionality l10n-platform Localization platform issues (not wrong translations)

Comments

@alexdima
Copy link
Member

Testing #4018

IMHO, there is a case not covered well enough. e.g.:

  • having Windows locale in English and wanting to run VSCode in Spanish.
  • or having Windows locale in Spanish and wanting to run VSCode in English.

The only way to do this now is to use a command line argument.

But especially in Windows, it is unusual to launch a UI app from the command line with arguments. E.g: taskbar, windows start button, double clicking a file associated with VSCode, right click open with VSCode.

I suggest some alternative means to define the locale besides the command line argument.

@dbaeumer
Copy link
Member

All we could do is a setting. But it can't be our settings store since this comes in to late.

@dbaeumer dbaeumer added l10n-platform Localization platform issues (not wrong translations) feature-request Request for new features or functionality labels Mar 14, 2016
@dbaeumer dbaeumer added this to the Backlog milestone Mar 14, 2016
@alexdima
Copy link
Member Author

I think putting on the backlog is a bit too optimistic, since this is a "breaking change".

If I have Windows locale set to German, VS Code always started up in English.

Starting with the March release, VS Code will start in German and it has no way to durably disable this behaviour.

@dbaeumer dbaeumer removed this from the Backlog milestone Mar 14, 2016
@dbaeumer
Copy link
Member

I could argue that it is a feature that was missing :-). I understand your point but I think for the majority of the users the new behavior is correct. The reasons is:

  • either your native language in non English and you configured your OS to your native language. Then you prefer the native language over English and VSCode will honor that with the March release
  • your native language is non English but you configured the OS to English. Then VSCode starts in English.

I don't really see why a German would configure the OS to German and want to have VSCode in English. If his English is good enough for VSCode then I guess he would run the OS in English.

We can discuss tomorrow in the standup. Given that fixing this requires additional work/features I moved it to the backlog given the 'minor' value I see.

@bpasero
Copy link
Member

bpasero commented Mar 14, 2016

Accessing our settings from main side is easy, I commented on a duplicate of this one.

@dbaeumer
Copy link
Member

Dups #4170.

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality l10n-platform Localization platform issues (not wrong translations)
Projects
None yet
Development

No branches or pull requests

3 participants