Translation in general

[arockenberger]

Since I want the workshop material to be used as self-study material and reference after the workshop is taught, I want it to be as accessible as possible. Therefore, I think translations into the languages I teach the workshop in are a good idea.

I am, however, unsure how to do this in the most effective and meaningful way.

1. Should I have one repository for each language or keep all in the current repository?
2. Should I translate every part of the lesson, incl. the glossary and reference list, or only the main lesson (as a follow-along-guide)?
3. How will I keep everything updated and equally well maintained if I have to keep track of 3 instead of 1 language-version?

Do you have suggestions? @lexnederbragt @sdruskat @yngvil

[lexnederbragt]

Maybe ask the people that translated some of the Software Carpentry lessons to Spanish, see https://software-carpentry.org/lessons/...?

[sdruskat]

Have a look at https://github.com/swcarpentry-i18n by @dpshelio. David has set up a translation infrastructure for SWC lessons :).

[dpshelio]

Hey! I'm happy to help. If you want to keep them all in sync based on a master language, then you could use what I'm proposing for the carpentries at @swcarpentry-i18n, this is with gettext and po files. The way it works is via tokens coming from the master language, that then need to be translated in these po files. They then can be converted into markdown. There are also tools that integrate this with github, making the whole process less manual