Open AvogatoWizardWhisker opened 4 months ago
Is this still happening/? We haven't had any other reports on Canary of this happening, and that build is a couple months out of date.
I'll try to retry again, and i'll let you know if the problem presists.
I apologize for the late response. I tried that again with Terminal Canary version: 1.23.2961.0. The issue still persists.
Do you think it has to do with administrative settings?
I don't believe so. The first item in each of these ("Display Language" in English) should be the one what the app platform should use for determining the language for WinUI. I think the language settings in the registry for Windows Terminal may have gone out of sync with the rest of the OS for you. @DHowett for instance encountered a bug just yesterday where he changed the "accent color" (the window border frame color) and Windows Terminal did not adopt it. He checked the package registry and it still contained the old value. I think these may just be various bugs with the packaged app / app platform implementation on Windows. 🤔
As you probably already know or noticed, you can change the "Language" setting in the left half of your screenshot (roughly in the center) to French and it should work around the issue. I'm not sure if we can fix this on our side since we rely on WinUI which in turn relies on the ApplicationLanguages.Languages
API.
Windows Terminal version
1.22.1781.0
Windows build number
10.0.26241.5000
Other Software
No response
Steps to reproduce
Expected Behavior
I'm expecting the language in Terminal to match with the OS since it should follow the system default
Actual Behavior
Even tho Terminal's setting language uses the "system default", it remains the same previous language.