2018-08-28 05:11 EDT, "DVD PS" <[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: discuss Permalink: https://carpentries.topicbox.com/groups/discuss/Tdb042c4bc0ecf365-M16279ab9bf8409e8faa1e004 Delivery options: https://carpentries.topicbox.com/groups/discuss/subscription
