-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Translator: enable in-page language switching #159
Comments
This issue has been marked as stale because it hasn't been updated in a while. It will be closed in a week. If you would like it to remain open, can you please comment below and see what you can do to get things moving with this issue? Thanks! 🙏 |
This was referenced Nov 7, 2020
This was referenced Jan 18, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be really helpful if translators and developers had a persistent switch they could use to allow them to change languages on any page (versus having to go back to
/me
to do it). The i18n code was already written with this type of feature in mind. This could be done as a bookmarklet or maybe a browser extension, but it would be great to have this as part of the community-translator widget. That would mean it would need to be persistent though, rather than only appearing when in a non-english language (although obviously still limited to people who have enabled it).This would be helpful for translators to spot check different pages, and also for developers to find translation bugs. For example, we found a bug from a mistranslated string in Spanish, but it was more difficult than necessary to determine it was the actual translation at issue versus the
translate()
request. If we had a persistent language-switcher, that would be a lot easier.If we don't want to make that translator toggle persistent, we could at least bring it up based on some keyboard command (still limited to people who have enabled it). Konami code anyone?
/cc @deBhal
The text was updated successfully, but these errors were encountered: