Handling/Supporting Translations

[markusmo3]

Hello everybody,
so i recently got an email from a nice Brazilian developer who wants to translate our repo for his people. Im not sure if he wants to be in the spotlight so i wont give any names.

But the main question is:
Do we want to support translation on our side ? Or should he just copy/fork our repo?
On the technical side it would be quite the work to get i18 or multi-language support working with the website, especially if we just do branches for all the other languages.
The most impacting change would be that we wont be able to use the github-pages autobuild anymore and would have to build manually with travis or sorts because we need a specific i18n jekyll plugin.

I think the easiest route would be to convert to an organization and do it similar to DiscoverMeteor

@iluwatar @npathai Some input on this maybe ?

[iluwatar]

I think this feature should definitely be on our roadmap. Not the whole world runs on English.

In general I like the way they put it together in DiscoverMeteor. There would be separate language files and the correct one would be referenced in the web site config. I understand this would require significant design and implementation effort. Would the person who suggested this be willing to work on this?

[markusmo3]

probably a good idea to use this: https://github.com/untra/polyglot
or this: https://github.com/vwochnik/jekyll-language-plugin

sauce: https://github.com/planetjekyll/awesome-jekyll-plugins

[iluwatar]

👍

[npathai]

Totally up for this 👍

[dougg0k]

Hi @markusmo3 If the person who wants to translate needs any help, I'm open to help.

[callmecolor]

I think we should. I not sure he's tryna get spotlight though. Thonk....

[iluwatar]

Moved to iluwatar/java-design-patterns-web#3