My two cents from a bilingual organization in Canada :
From our experience at Compute Canada (we produce most of our written
content in both French and English), having *separate* content is a
recipe for one of them to become outdated. What we found works well is
MediaWiki with the Language Extension bundle. I wrote a
software-carpentry-style lesson about OpenACC programming using that here :
https://docs.computecanada.ca/wiki/OpenACC_Tutorial
What makes things easier with this way is that
1) each page is disentangled into multiple translation units
automatically, by the extensions
2) the extensions provide us with a quick way to spot outdated or new
translation units, which we can then translate :
https://docs.computecanada.ca/mediawiki/index.php?title=Special%3ALanguageStats&x=D&language=fr&suppresscomplete=1
I don't know that it is possible to do something nearly as convenient
with just gh-pages...
Regards,
Maxime
On 2018-08-28 6:30 PM, Rémi Rampin wrote:
2018-08-28 05:11 EDT, "DVD PS" <[email protected]
<mailto:[email protected]>>:
So, over the last months, I've been working to get something that
eases the work of the translators and provides all the languages
the same visibility - i.e. one page for all!
Hi David,
I wonder if this is the right approach. There is no real benefit in
having everything be in the same repository, so long as you have links
pointing to the other languages. In fact, I am not sure if
git-novice-_*es*_/01-basics/ is worse than
git-novice/*_es/_*01-basics/ (or the current
git-novice/*_es/_episodes/_*01-basics/).
I think having separate repos (or branches) for different languages
would make it much easier to keep the translation up-to-date, since
you can use Git merges in the usual way to see what have changed in
the upstream (e.g. the English lesson) and update your translation.
I see that you are not far from this since you are in fact using a
submodule, however:
* submodules are error prone (especially in sub-directories), it is
likely that contributors or even maintainers will get this wrong
* the build process gets more complicated (do contributors to the
translation have to clone the outer project instead of the
translation?)
* the submodules for each translation will need to be updated in the
outer repo for changes in the translation to appear on the site
* you cannot have the translation be a branch that you merge from
the English upstream (infinite recursion)
What do you think?
--
Rémi
*The Carpentries <https://carpentries.topicbox.com/latest>* / discuss
/ see discussions <https://carpentries.topicbox.com/groups/discuss> +
participants <https://carpentries.topicbox.com/groups/discuss/members>
+ delivery options
<https://carpentries.topicbox.com/groups/discuss/subscription>
Permalink
<https://carpentries.topicbox.com/groups/discuss/Tdb042c4bc0ecf365-M16279ab9bf8409e8faa1e004>
--
---------------------------------
Maxime Boissonneault
Analyste de calcul - Calcul Québec, Université Laval
Président - Comité de coordination du soutien à la recherche de Calcul Québec
Team lead - Research Support National Team, Compute Canada
Instructeur Software Carpentry
Ph. D. en physique
------------------------------------------
The Carpentries: discuss
Permalink:
https://carpentries.topicbox.com/groups/discuss/Tdb042c4bc0ecf365-M0ae9399ed69dc884844c20a8
Delivery options: https://carpentries.topicbox.com/groups/discuss/subscription
