SWC i18n maintainer's meeting

2019-12-24

Attendees (all online)

• @rikutakei
• @TomKellyGenetics
• @joelnitta

What to (git) ignore

Can we ignore these?

• mo files
• pot

Didn't get to this. Joel will follow up.

• pot files are the raw (untranslated) output from the scripts
  • we can delete (or move this) as they're repaced by *.ja.po, etc.
  • so yes, I think (Tom)

_locale

Why is _locale in the git-novice submodule? As long as it is there, Spanish md files will get pulled in everytime we use po4gitbook/update.sh.

Tom is going to change the submodule we use for git-novice, which shouldn't have _locale in it.

Submodules

When to update submodules?

SWC may be implementing a versioning system for lessons soon. If they do this, it will be much easier to peg a translation to a certain lesson version. For now there is no clear way to decide when to update submodules.

po4gitbook/update.sh

I tried po4gitbook/update.sh after removing _locale from git-novice. It seemed to reformat line breaks for existing translations. Is this expected behavior? I'm assuming it won't cause any problems with translations, but it's kind of annoying because it's hard to tell what it just a reformatted line-break and what is really changed content.

Probably just line-breaks. Only way to tell is by rendering the webpage. We are working on a way to automate this so it should be immediately apparent if something is weird.

Workflow

Is Spanish actually using the translation repo right now? Looks likes it's only got md files, wouldn't make the complete web page.

What about a way to automate everything from updating PO file to generating web page? Would be nice to verify that a given PR didn't break anything.

Along those lines, what about setting up CI e.g., with travis?

mergify

I set up a test repo to try it out.

• Have a look at this PR. If somebody approves it (I can't!), it should merge automatically.

• This is about as simple as rules get for mergify. Should be no problem to implement for i18n.

Joel will set up mergify for the repo (PRs will be automatically merged after passing one review).

We could even integrate it with travis / circle-ci if we felt really ambitious.

Documentation

see Issue 34

• Where to put all the docs?

• How to handle JA/EN versions?

Joel will make a docs/ folder and put everything in there

TODO

1. figure out semi-regular calls
   a) Japanese core team
   b) technical people
   c) SWC internationalisation people
   (Dave ES + Github, Rayna & Paula + ES, Victor KO, Raniere Silva BR-PR)

2. figure out the whole PO compilation process - Joel
   a) submodules and _locales - is there a better way to implement this

   • make a pretty picture of this and run by Dave?

3. a) script to render HTML from POs - Everyone / Tom (x WIP)
   b) integrate with travis (if we can get it to work)

4. want a Japanese rendered website for reviewing as we translate materials
   a) set up gh-pages for -ja repos to render on itself (not multi-lingual) for testing

   • current english repos render on gh-pages and display ja or es from master branches

5. english lesson for r-novice-gapminder (test multilingual lessons) - Tom?

   • run git4po scripts on lessons
   • others forked from carpentries-i18n
     if it fails contact Dave PS
     (reached out to David Perez-Suarez as it globe doesn't render)

6. clean up git-novice repo (start fresh?)
   a. un-fork remove github repo and push new local copy –Tom (o)
   b. clean up and continue translating - Riku

Alpha. Spread the word, get people involved.