Translatable interface

[hugoroy]

The scripts, especially render.js should allow for translations. Right now, people have to dive-in render.js and edit the code to translate every piece in English to their own language. IMO that's okay for the HTML code, but not for the basic functions of the website.

[gabriel4649]

I can work on this task. I was thinking of using i18next for the task. What are your thoughts on using that library for this task? Did you have a particular solution in mind? Are there any guidelines I should follow for this task. Thanks for your great work on tosdr!

[michielbdejong]

@climatewarrior great! basically only two things to keep in mind:

• document how the build instructions change (if at all)
• document how people can add a language (i.e. point to whatever file they should add/change to build the site in a different language).

the current build process is documented in the README file, it's basically "sh build.sh" :)

[gabriel4649]

@michielbdejong Great! I will start working on it soon. I will submit a pull request later on.

[hugoroy]

@tatsuhirosatou hello, any news about this? We're going to work on this maybe for tosdr.org/conf -- it would be nice if you could join on irc.freenode.net #tosdr

[JustinBack]

Translations are now possible via Crisp!

https://github.com/JustinBack/CrispCMS-ToS-DR/tree/master/translations