Wiki instructions to merge updated translations are obsolete
Hi there, I just wanted to point out that the instructions in points 6 and 7 of the Wiki article https://wiki.inkscape.org/wiki/index.php?title=Interface_translation don't work. In step 6, when I click "Replace" and upload my new file, I get the message: "*You are not allowed to push to this branch*" [image: screenshot_2022-08-17_at_11.38.28.png]
Previously, I have been successful in forking the entire project on gitlab, commit the file to my own fork in a new branch that I create just for the updated es.po file and create a merge request from there. The problem with this approach is that, when a new release comes out, my fork is so outdated that a new merge request causes nothing but trouble. Having to do this every couple of months seems too cumbersome, especially if you're not familiar with git, as I suspect most of our translators are.
Is there any other, easier, way to submit updated po files that I'm overlooking?
Thank you in advance, -- *Lucas Vieites* Blog @ codexion.com https://blog.codexion.com/ LinkedIn https://www.linkedin.com/in/lucasvieites
Hi Lucas,
I think GitLab has deactivated automatic pull mirroring for free. Not sure.
You can work around that by using the command line to update your branch... Or delete your fork, and create a new one (there's no option to do that updating manually via the web interface).
And never ever commit to the master branch in your fork, that one is reserved for just copying Inkscape's.
Sorry, I know it sucks. Nothing I can do about it, though...
Kind Regards Maren
Am 17.08.22 um 11:59 schrieb Lucas Vieites:
Hi there, I just wanted to point out that the instructions in points 6 and 7 of the Wiki article https://wiki.inkscape.org/wiki/index.php?title=Interface_translation https://wiki.inkscape.org/wiki/index.php?title=Interface_translation don't work. In step 6, when I click "Replace" and upload my new file, I get the message: "*You are not allowed to push to this branch*" screenshot_2022-08-17_at_11.38.28.png
Previously, I have been successful in forking the entire project on gitlab, commit the file to my own fork in a new branch that I create just for the updated es.po file and create a merge request from there. The problem with this approach is that, when a new release comes out, my fork is so outdated that a new merge request causes nothing but trouble. Having to do this every couple of months seems too cumbersome, especially if you're not familiar with git, as I suspect most of our translators are.
Is there any other, easier, way to submit updated po files that I'm overlooking?
Thank you in advance,
*Lucas Vieites* Blog @ codexion.com https://blog.codexion.com/ LinkedIn https://www.linkedin.com/in/lucasvieites
Inkscape Translators mailing list -- inkscape-translator@lists.inkscape.org To unsubscribe send an email to inkscape-translator-leave@lists.inkscape.org
participants (2)
-
Lucas Vieites -
Maren Hachmann