Changing Windows default display language doesn't affect Chrome |
|||||
Issue descriptionVersion: 49.0.2623.87 OS: Windows 10 What steps will reproduce the problem? (1) Install Win10, go through Windows-Updates, keep en-US as display language (2) Install Chrome (49.0.2623.87 (Official Build) m (64-bit)) (3) Change default display language of Windows to Russian (i.e. see http://www.howtogeek.com/232659/how-to-change-the-display-language-in-windows-10/) (4) Sign out of Windows, sign-in back in, launch Chrome What is the expected output? What do you see instead? I expect both Windows and Chrome to start displaying Russian UI strings. Actual behavior I see is: - Windows speaks Russian (i.e. Russian entries in the start menu instead of "Settings", etc.) - Problem #1: Chrome continues to speak English (i.e. "Chrome Browser" as Window title, "New tab" under hamburger menu) - Problem #2: Chrome continues to ask for English over HTTP (i.e. https://www.google.com/chrome/browser/desktop/index.html is displayed in English).
,
Mar 14 2016
Obviously, adding and changing the language via chrome://settings works, but I was expecting the os-wide settings to also take effect (without the user having to dig into Chrome-specific settings).
,
Mar 22 2016
After some discussion on the Chrome Windows team list, we propose the following: * Leave how Chrome's initial language is selected alone -- it will still get this from the download page * Monitor the user language (i.e. the one returned by GetUserDefaultLangID()) and map it to an appropriate Chrome language * If this value changes, and the old value matched the current Chrome UI language, set the new language as the default UI language, adding it to the language list if necessary We didn't discuss whether to remove the old language from the language list. It's not obvious to me what behavior would be better there.
,
Mar 23 2017
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue. The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 24 2017
This is not a localization bug.
,
May 24 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by lukasza@chromium.org
, Mar 14 2016