Skip to content

Instantly share code, notes, and snippets.

@sotayamashita

sotayamashita/i18n.md

Last active March 12, 2018 06:31
Show Gist options
  • Save sotayamashita/2faf2ddae2ac89ba39255bba48543166 to your computer and use it in GitHub Desktop.
Save sotayamashita/2faf2ddae2ac89ba39255bba48543166 to your computer and use it in GitHub Desktop.
Download ZIP
Node.js community localization problems (in my opinion)
Raw
i18n.md

Before digging deep, we need to clear problems for community localization:

  1. NO way to know the diff between a source and localized one
  2. NO a localization workflow

1. NO way to know the diff between a source and localized one

-> I hope it can be solved with Crowdin.

2. NO a localization workflow

It might be big scope so I divided this topic into 2 step:

2.1. Set moderators for each language

It makes it very easy for us to handle localization workflow so we need to set a moderator for each language. Vue.js community is very useful in terms of community localization. They set moderators for each language and each moderator to have responsibility to review translation. Crowdin has a feature for it. https://support.crowdin.com/advanced-workflows/

2.2. Gather volunteers

After setting moderators for each language. It's time to gather volunteers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment