Hi David, Thanks for all your efforts on this. I've had a go with your template and it seems to work for Japanese. See the demo here!
https://tomkellygenetics.github.io/git-novice/ja/index/index.html It's a quick hack-job on the translations but the assets support Japanese characters. I really should get a native speaker to do a peer-review on them since I haven't learned much programming terminology in Japanese yet. Once I figured out which repo to run the commands in, it worked pretty smoothly but that took a while to figure out. Perhaps we need a more detailed readme/guide on which repos they'd need to clone or make changes to for new translators (although I guess we only need to set up the themes once per language). It could certainly save time for future translations but I've got a few reservations on how it would work based on my experience with the system. Editing the PO files works pretty well on your own but I'm not sure how this would work in a team. Would we need to separately translate each core lesson or would it be possible to split this task up over github (at the moment these fields aren't tracked in the workflow but I think they could be). While this is a great way to get latest version of the English lessons, it seems to require starting over on the translation each time there's an update or is there are way track changes to the PO files and only translate fields that have been changed? Thanks, Tom Kelly ------------------------------------------ The Carpentries: discuss Permalink: https://carpentries.topicbox.com/groups/discuss/Tdb042c4bc0ecf365-M8cc25ce3a5046c7219318ac3 Delivery options: https://carpentries.topicbox.com/groups/discuss/subscription
