-
Notifications
You must be signed in to change notification settings - Fork 865
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
Web UI and Desktop languages #844
Comments
Depends who is the target audience. I believe the goal is to encourage contributing missing translations, so we should not be hiding them. We crowdsource translations from community. To get to translation parity between Web UI and Desktop we should surface missing translations, so potential contributors see what is missing. I'd go with low hanging fruit: "Change Desktop's language according to Web UI's". If we want to go extra mile, Desktop could also display a message asking user if they would like to contribute missing translation, clicking Yes would redirect them to https://www.transifex.com/ipfs/ipfs-desktop/) |
First part is done, we now need to drive the extra mile.
|
This is something trivial to do. @lidel @jessicaschilling do you think this is still useful? |
Yes! |
Maybe a dialog when a person opens IPFS Desktop for the first time and then leaving a button on the menu to contribute (maybe under About)? |
Only for folks for whom their chosen WebUI language doesn't exist in Desktop, right? If so, that sounds good. |
Uh, I get it now and it may be more complicated than what I thought then. I'll investigate, but it is certainly possible. |
Makes sense to me. We can always revisit if necessary. |
Right now, Desktop gets its language from the operating system its running on and passes it to the Web UI. Although, the user can change the language of the Web UI via its Settings, which does not affect the language of IPFS Desktop and then we get a mixed UI.
I've got some possible options to solve this issue:
@olizilla @fsdiogo @lidel what do you think?
The text was updated successfully, but these errors were encountered: