ipfs / ipfs-webui

A frontend for an IPFS Kubo and IPFS Desktop
https://webui.ipfs.io
MIT License
1.55k stars 484 forks source link

Add support for multiple languages since the beginning #675

Closed hacdias closed 6 years ago

hacdias commented 6 years ago

We should add a library to support multiple languages right from the beginning to make it easier to expand after this revamp is finished. What do you think?

/cc @olizilla @lidel @alanshaw

olizilla commented 6 years ago

💯

Current state is documented here: https://github.com/ipfs-shipyard/pm-ipfs-gui/issues/50

of note, crowdin is the localization service of choice for node js and electron

lidel commented 6 years ago

Keep in mind that setting up a unified crowdsourcing website for all GUI apps should be done at the end of revamp endeavor to decrease noise/breaking changes until we have all screens implemented.

Until then, there are things that need to happen first:

Digression: The key is to respect time of translators and do not ask from contributions until we are sure locales work as expected and won't change drastically. For example, when initial revamp work is done, we could smoke-test translation process by adding Polish and Portuguese locales to iron out all kinks before opening project to accepting external translations via crowdsourcing site.


Meta issue for GUI Translation Project: https://github.com/ipfs/ipfs-gui/issues/50

lidel commented 6 years ago

I think we've done it all :sparkles: :rocket:

WebUI uses i18next with JSON+ICU format and we a fancy crowdsourcing website for translations (context: https://github.com/ipfs/ipfs-gui/issues/50):

Source strings (en) are synchronized once a day.

screenshot_25