cgeo.github.io
cgeo.github.io copied to clipboard
cgeo
FAQ translation
I want to start a new approach of asking the community for help in translating the FAQ.
For this reason I started a small Wiki page describing some basics (for people not used to Github) about how they can contribute.
Maybe someone (@SammysHP ?) can review the wiki page and make additions/corrections where needed.
https://github.com/cgeo/cgeo.github.io/wiki/How-to-contribute-translations-for-the-c:geo-FAQ
Wouldn't be easier for translators to use the crowdin platform? I think they can handle .yml files.
Le 2017-08-17 16:01, Lars a écrit :
I want to start a new approach of asking the community for help in translating the FAQ.
For this reason I started a small Wiki page describing some basics (for people not used to Github) about how they can contribute.
Maybe someone (@SammysHP [1] ?) can review the wiki page and make additions/corrections where needed.
https://github.com/cgeo/cgeo.github.io/wiki/How-to-contribute-translations-for-the-c:geo-FAQ
-- You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub [2], or mute the thread [3].
Links:
[1] https://github.com/sammyshp [2] https://github.com/cgeo/cgeo.github.io/issues/152 [3] https://github.com/notifications/unsubscribe-auth/AAKymu3rviYv32000n5MFnUOYpoVXDOUks5sZEfSgaJpZM4O6TuA
Also we should probably add one file for each language (as suggested earlier in my second draft).
We have issues for both topics AFAIR. But as none of these is true until now, I wanted to go another way. But if one of you is interested to bring it to crowdin, that would be even better.
@shroudedcode Are you maybe interested to help with making the hompage "compatible" with using a translation service (i.e. Crowdin) in our case? Some ideas are mentioned above already.
I think it would help a lot to have the whole page (or at least the FAQ) localized in more languages to allow users to help themselves in case of questions/problems.
@Lineflyer If we were using a more flexible static site generator/web server solution, I'd say yes. But I really don't want to do this with Jekyll, because I would probably have to implement it in a kind of hacky way which is often the case with Jekyll.
electronjs.org which previously used Jekyll as well switched to a custom Node.js solution because of this which allowed them to implement a great system for localization. I also use Node.js to build my personal website and it's just great.
In other words: I'd rather rebuild this site from scratch using a custom Node.js build process than having to work around Jekyll's limitations or wait for certain plugins to be allowed on GH pages.
