search

jsha / blocktogether

Share your blocks and subscribe to others'
GNU General Public License v3.0
330 stars 68 forks source link

Internationalization #155

Open jsha opened 9 years ago

jsha commented 9 years ago

Pick an internationalization framework and replacing the strings with appropriate placeholders.

doeg commented 9 years ago

Looks like there's a helpful article from John Resig about this: http://ejohn.org/blog/a-strategy-for-i18n-and-node/. And another from Mozilla: https://hacks.mozilla.org/2013/04/localize-your-node-js-service-part-1-of-3-a-node-js-holiday-season-part-9/

jsha commented 9 years ago

Thanks for doing this research @doeg! Worth noting that we can get a pretty reliable language indicator from the Twitter user object on signup. We will want an override for that in case someone finds that Block Together in language X is poorly translated. That override can probably go in settings.

For our translation platform, I'm going to suggest using Transifex, since it's free for open source projects, and I've used it a tiny bit for HTTPS Everywhere (but I need to get better at using it).

jeromecc commented 6 years ago

Hello @doeg & @jsha! Which solution would you suggest to start the i18n process? I'm interested in providing a French translation. I can work on the internationalization of the code but I'd rather follow the lead of people who have more experience with node and this project as to which solution is best. Thanks.

jsha commented 6 years ago

Hi @jeromecc! Thanks for the ping. I honestly don't know which node package is the best for translations. If you could research and help pick one as part of working on this, I'd greatly appreciate it. Thanks!