Hello Maurizio, I had the same problems translating the manual into German. I had two contributors for the translation. One of the supporters had experience with github. I had agreed with him the process you have described. He creates pull requests on my darktable fork, which I reviewed and entered into the translation. The second supporter had no experience with git, with him I shared the po file directly via email. I transferred his changes to my po file by comparison.
I would also be very interested in a simpler strategy! How do the other translators solve it? How is this handled in other projects? Who has experience? Cheers Pierre > Von: "Maurizio Paglia" > Datum: 24. September 2019 um 15:28 > An: "Darktable Developers List" > Betreff: [darktable-dev] GitHub question for translation > > Hi all, > do we have a standard method for a collaborative translation? > > I can explain better. > This year the Italian translators have one volunteer more. > I desire to collect his translated strings in order to check and validate > them before pushing on dt master branch. > For this reason I asked him to send pull requests to my fork so I can > validate them, nerge them and push to dt master branch. > > It sounds a little bit complicated... > Can you advise if we have a more linear method? > > Thanks, > Maurizio > ________________________ darktable developer mailing list to unsubscribe send > a mail to darktable-dev+unsubscr...@lists.darktable.org ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
