-
Notifications
You must be signed in to change notification settings - Fork 122
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
Date language mixup #3176
Comments
This is an artifact of the time locale being able to be set independently of the language in settings. |
FYI: In the context of 'mai', 'juin' is most likely French. |
Thanks! Post updated |
@Sheikah45 Were you able to reproduce it by description? I tried to look into, but the date is following a user's setting of preferred language. Tried multiple combination. @Backspace345 If you change a language(to somethign different) and restart the client, is it still same? Do you still get french one? Even when you get back to origin language? Tested on Win11. |
@sulikdan yes, tried multiple times now, for some reason it just stays there. Complete reinstall removed the bug though. I wonder if it's because my windows install broke once. Due to that i had to reformat drive with it, which apparently contained some of the metadata client files, but the client itself was installed on a separate drive, and after reinstalling windows i just went to the client folder and created a shortcut manually. Surprisingly enough it worked just fine. So i guess there never was any issue? |
@Sheikah45 can I take it? |
In terms of fixing it sure. |
Describe the bug
In leaderboards tab the current season period is shown in French, while client language is set to English. Changing client language doesn't change date language in leaderboards. Date format in settings is set to Day/Month/Year, if that's related.
To Reproduce
Go to settings > appearance, set date format to Day/Month/Year, go to Leaderboards tab.
Expected behavior
Dates changing according to client language.
Screenshots
OS
Windows 10
The text was updated successfully, but these errors were encountered: