-
-
Notifications
You must be signed in to change notification settings - Fork 959
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
Preferred language when not logged in #8937
Comments
This issue seems to be a good fit for newbie contributors. You are welcome to contribute to Weblate! Don't hesitate to ask any questions you would have while implementing this. You can learn about how to get started in our contributors documentation. |
The logic is here: weblate/weblate/accounts/models.py Lines 691 to 700 in a58b7f3
Adding the current interface language is the easiest path, but that would limit it to only languages in which Weblate is translated. Building on top of |
Hey @nijel, I'm starting work on this. What do you mean by "Adding the current interface language"? If extending on |
|
So if the user is not logged in, 1.) Get language from header using Let me know if that sounds right. |
Yes, |
…dering This shows more prominently translations user understands. Fixes WeblateOrg#8937
…dering This shows more prominently translations user understands. Fixes WeblateOrg#8937
…dering This shows more prominently translations user understands. Fixes WeblateOrg#8937
…dering This shows more prominently translations user understands. Fixes #8937
Thank you for your report; the issue you have reported has just been fixed.
|
Describe the problem
Preferred target language not detected when not logged in.
Describe the solution you'd like
Display the browser's display language at the beginning of the language list. Same as when login.
Additional context
"日本語 (Japanese)" is displayed at the bottom of the list due to the rules of Japanese. They have to scroll to the bottom every time. The languages at the bottom in Unicode order have the same problem.
The text was updated successfully, but these errors were encountered: