Hi Tom!!!
> 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. > I'm almost crying of happiness!!! Seen the menu with the three languages is super nice!!! And with Japanese characters! I love it!!! :) > 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). > For sure!! A lot need to be added to the readme. Even though if that work to add a language is not intended for the translators, but for the maintainer of the "translation-hub". > 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). > You are 100% right! The workflow can be improved. I'm happy you found the PO file usage confortable. A possibility of work sharing could be distributed by messages number. So say you and I are translating a particular lesson we can say, you translated from 1 to 399 and I go from 400 to 792. Then two PR where each of us review others work. This would be the approach that less overheads on other tools introduced, but not the simpler. I've been playing with a tool called zanata (http://zanata.org/) which could make the collaborative work easier (and more attractive). That platform allows to pull/push from the command line, so makes the automation to build translated work eassier. I've been trying to simulate how that platform updates when I push an updated English content and seems to provide the previous translation of the changed segment as a suggestion - besides suggesting text from different projects with similar text. This last point is very good to know how other projects refer to technical words. I can add you (and anyone) to the play-project https://translate.zanata.org/project/view/swc-git-novice/?dswid=-8716 The next tool I'm going to play with is https://weblate.org/ > 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? > I hadn't have that problem... in my case, once you run "update.sh" will mark the translation as "fuzzy" and will show it in the same place. I've tried adding new paragraphs and still that works. In any case, I believe the translations are easier when the content is fixed, that's why I prefer that translations happen, mostly, on a release by release basis. In big software projects (gnome, kde, mozilla are the one I know) they leave a couple of weeks before the release fixed so translators work on getting all the "stuff" translated. Then the release is done for everyone. That is my dream for software carpentry material :) > Thanks, > Thank YOU!! David ------------------------------------------ The Carpentries: discuss Permalink: https://carpentries.topicbox.com/groups/discuss/Tdb042c4bc0ecf365-M82db0ac3d3910eab8e6ff64b Delivery options: https://carpentries.topicbox.com/groups/discuss/subscription
