At the moment some of the po files in the manual repository are quite outdate compared to the po files on pootle. Before branching out the manual, could we do a general update on all po files for the manuals 21.05 and 20.11? I know it would help a lof for German, but I think doing it for all languages every half year would be good as a lot of people are not aware of the process and wouldn't ask for updating.
Thanks for raising Katrin. I'm still getting my head around the translation process (I should really know this by now). I'll write up how I think it is supposed to work in the Wiki (probably https://wiki.koha-community.org/wiki/Translating_the_Koha_Manual), and incorporate the material from https://gitlab.com/koha-community/koha-manual/-/issues/13#note_243241096 Then I'll ask for feedback - to make sure I've got it right, including the specific steps! David
Thx, David. I think Martin/Caroline might also be able to help a bit. We really need to write things down.
I've made my first attempt on documenting the steps - still needs some work: https://wiki.koha-community.org/wiki/Documentation_management#Translating_the_manual
I'm still not 100% clear on the process to update the translations for 20.05 and 20.11. ** Update the translations on koha-community.org/manuals ** 1. Follow step 6 - pull request, merge into repository -> builds run and update k-c.org OR 2. Use secret URL to make the pull request? ** To get Pootle updated with changed strings ** Contact Translation manager and ask for strings to be updated. Or do I use the tools to update the .po files in the repository for the versions: 1. Create a branch 2. Locally run: make gettext 3. Tidy ups to .po files? 4. Commit and push to branches on GitLab: Translation update - manual - 2021-12-XX
(In reply to David Nind from comment #4) > 3. Tidy ups to .po files? That should have said .pot files!
Hi David, not sure about the process, but you don't want to update the po files locally (your last option). The translation work is already done on another repo and "just" needs to be merged in.
Hi David, reading the wiki page: String freeze Currently we have no string freezes for the manual as it doesn't have a real release date. The translation files on translate.kc.org used to be updated more continuously I think - but I don't seen an update for your latest changes: https://translate.koha-community.org/de/ (last update 7 months ago) I think the current string freeze for Koha is already quite short, which makes it hard to finish the Koha translations in that amount of time. Adding the manual to it would be too much I think. I'd prefer having a monthly update of po files at least or even better continously updates whenever a change is made. Especially since we have been backporting fixes/corrections to older versions of the manual. I believe using the "magic url" to make pull requests for the each language would work, but maybe there is an easier way to do them all at once? And it's currently missing 21.05 in the pull down.
(In reply to Katrin Fischer from comment #7) >.. Adding > the manual to it would be too much I think. I'd prefer having a monthly > update of po files at least or even better continously updates whenever a > change is made. Especially since we have been backporting fixes/corrections > to older versions of the manual. Now that I'm figuring things out, I think monthly would make sense. I've updated the page to reflect this. > I believe using the "magic url" to make pull requests for the each language > would work, but maybe there is an easier way to do them all at once? And > it's currently missing 21.05 in the pull down. The "magic URL" seems to only be for Koha itself, so I've used the other page - pull requests for 20.05 and 20.11 made. I will ask Bernardo about updating it so 21.05 is available that way. David
There's a magic URL from manual translations too I believe. I'm happy to help on automating more of this.. I did do some work last cycle to automate the merge requests but I can't remember what state we got to.
Thanks Martin! Happy to figure out and run any manual steps required in the meantime. David