Switch to transifex for translations

[saivann]

All strings, urls and anchors are now in a single yml files for each language
Translations in html are generated by a jekyll tag plugin
Each html file remain independant of each other

Update:
All strings, urls and anchors are now in a single yml files for each language
Translated html pages are generated by a jekyll plugin based on unified templates

This change can allow to handle translations in a more efficient way. Allowing more translators to work without learning technicals behind github, html and such. Making translations updates more obvious and easy to handle. And it allows to have more reviews and teams in charge of each translation.

[saivann]

I am still a ruby and jekyll newbie, so if someone see a better way to do this, or any improvement, I'm listening with attention. However, I've tested it enough with transifex to say that it works well and that it can fulfill everything we need, to my knowledge.

@tcatm : You were talking a week ago about using a jekyll plugin for translations if I remember correcly. Does that go in the sense of your idea?

[saivann]

This big change is almost ready to be merged. Last call for last minute reviews and comments.

Edit : This change won't be pushed until the hardfork and the conference is over.

[saivann]

I've updated the pull request to use unified layouts and templates for all pages as per tcatm feedback. That makes things much easier to manage when it comes to translated urls.

[tcatm]

ACK. Looks good to me.