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

winget is localized for my region, even when my UI-language is set to en-US #238

Closed
jessehouwing opened this issue May 20, 2020 · 13 comments
Labels
Area-External Issue outside of winget-cli source Area-Localization Issues related to localization Issue-Bug It either shouldn't be doing this or needs an investigation.

Comments

@jessehouwing
Copy link

jessehouwing commented May 20, 2020

Brief description of your issue

I am running an English version of Windows, but live in The Netherlands. So my UI culture and my region settings are different. All my apps should be defaulting to showing their UI in English, but the currency and date formats in Dutch.

winget shows most of its text as Dutch:
image

Steps to reproduce

Windows Country or region: The Netherlands
Windows Regional format: English (Europe)
image

Windows Display Language: English
image

Expected behavior

the text output from winget is English

Actual behavior

the text output is Dutch

Environment

Windows Package Manager v0.1.41331 Voorbeeld
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19041.264
Package: Microsoft.DesktopAppInstaller v1.0.41331.0
@jessehouwing
Copy link
Author

jessehouwing commented May 20, 2020

Found the reason. Because this is a store app, my Microsoft Account display language is used. This is pretty counterintuitive.

To see and change what your current language is, check the display language, the highlighted vaue was set to "Dutch (Netherlands)".
image

Then open the Microsoft store app and download updates. It may take a while for the setting to sync.

I consider this a bug, my Windows installation has a UI language set, applications should follow it, but I'm guessing this is a WinRT remnant from the phone era we're now stuck with. I'd like a way to override the display language through configuration.

See also:

@KevinLaMS KevinLaMS added the Issue-Bug It either shouldn't be doing this or needs an investigation. label May 21, 2020
@FaffeF
Copy link

FaffeF commented May 23, 2020

This mess is very common in Microsoft apps, and was a major annoyance for years in Windows 10. Please don't bring it back.

@KevinLaMS
Copy link
Contributor

Thanks for reporting this. I am struggling a little bit with the repo however. I am finding that the language for the client is responding to the Windows display language.
IMO, the language used by the client should come from Windows display language, so it is correct. Did it eventually update per the link you provided?

We can investigate adding a language override in options.
Thanks

@jessehouwing
Copy link
Author

Yeah, the appstore language change eventually synced to windows. I'm happily on English now.

It's funny how much of Windows assumes I will constantly deliberately switch between languages.

@FaffeF
Copy link

FaffeF commented Jul 10, 2020

I think I found out what my problem was: my Windows preferred language order was English (Sweden), Swedish (Sweden), English (United States).

This probably meant that Winget ignored English (Sweden) and went straight to Swedish. I don't understand the reasoning behind the separation between preferred language and Windows display language, but my expectation would be that if your app doesn't support English (whatever), just do English (US/UK/AUS/CAN), cause the differences are small enough that it doesn't matter.

Still didn't fix the Windows Store app.

@denelon denelon modified the milestones: Package Manager v0.2.x, Package Manager v0.3.x Aug 21, 2020
@denelon
Copy link
Contributor

denelon commented Jan 7, 2021

Is this issue resolved?

@denelon denelon added the Needs-Author-Feedback Issue needs attention from issue or PR author label Jan 7, 2021
@ghost ghost added the No-Recent-Activity Issue has no recent activity label Jan 14, 2021
@ghost
Copy link

ghost commented Jan 14, 2021

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment.

@FaffeF
Copy link

FaffeF commented Jan 16, 2021

Seems to work, adhering to the order of languages in the "Preferred languages" list, as output by Get-WinUserLanguageList.

This is probably correct, though as a user I can't really understand why there is a setting for "Windows display language" that is separate from "Preferred language"

@ghost ghost removed the No-Recent-Activity Issue has no recent activity label Jan 16, 2021
@ghost ghost added the No-Recent-Activity Issue has no recent activity label Jan 23, 2021
@ghost
Copy link

ghost commented Jan 23, 2021

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment.

@denelon denelon removed Needs-Author-Feedback Issue needs attention from issue or PR author No-Recent-Activity Issue has no recent activity labels Feb 3, 2021
@denelon denelon added this to To Do in Client-Bugs Mar 9, 2021
@denelon denelon added the Area-External Issue outside of winget-cli source label Apr 20, 2021
@denelon
Copy link
Contributor

denelon commented Apr 20, 2021

This issue appears to be related to how Windows handles language priority.

@denelon denelon closed this as completed Apr 20, 2021
Client-Bugs automation moved this from To Do to Done Apr 20, 2021
@denelon denelon modified the milestones: Package Manager v0.3.x, v1.0 - Windows Package Manager May 4, 2021
@denelon denelon added this to Done in Client-Current May 6, 2021
@yeya
Copy link

yeya commented Nov 23, 2021

We can investigate adding a language override in options. Thanks

Language override by options will be great. The default font of cli \ powershell doesn't support my windows display language so I like to set only winget to english.

@craftzdog
Copy link

Set-WinUserLanguageList solved the issue.

https://docs.microsoft.com/en-us/powershell/module/international/set-winuserlanguagelist?view=windowsserver2019-ps

@denelon denelon removed this from Done in Client-Current Jul 11, 2022
@PeterVeg
Copy link

Thank you, this is great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-External Issue outside of winget-cli source Area-Localization Issues related to localization Issue-Bug It either shouldn't be doing this or needs an investigation.
Projects
None yet
Development

No branches or pull requests

8 participants