Add translation system

[nutiteq]

My suggestion: http://www.transifex.com, upload .po files there and have them translated by community. It has working CLI tools so you can have even automatic pull/push workflow of new strings and translations.

[jmarlena]

Red Hat uses Zanata to manage the work of their translators. Would http://zanata.org/ work well here? Thoughts?

[jmarlena]

I found a really cool localization management tool called Crowdin that is free to open source projects.

Here are some sample screenshots from a Django Girls tutorial kept on GitHub:

We can try signing up for free at this link:
https://crowdin.com/page/open-source-project-setup-request

This tool has the potential to drastically simplify the current translation workflow & encourage more translation help. Any reason why we wouldn't want to test this tool to manage translations?

[jmarlena]

Potential Solution for issue #13, #138

[jmarlena]

Update: It looks like POEditor offers direct GitHub Integration (Crowdin doesn't at this time) and the process looks easier than Transifex's integration process.

PoEditor's GitHub Integration Setup/Process:
https://poeditor.com/help/how_to_translate_a_language_file_from_a_github_project

Transifex's GitHub Integration Setup/Process:
http://docs.transifex.com/integrations/github

I think POEditor looks like a good, easy-to-use & maintainable option.

[Nick-Tallguy]

Certainly we need to set in place a translation system. I don't know if @althio has had time to fully investigate Transiflex yet - I suspect not as he has been busy.

@jmarlena thanks for checking this out - could you prepare a workflow guide 'in rough' that we could compare with ? that althio may have, so we can work out which way to go.

Thanks for investigating this so far.

Nick

[Nick-Tallguy]

closing as we are using Transifex - working system, but am still open to suggestions as to making the system easier.