Hi translators,
Attempting to make the Inkscape translation process more inviting and easy to grasp, you can now use our Weblate instance, hosted on https://translate.inkscape.org , to translate Inkscape.
The proposed process is described into the readme of https://gitlab.com/inkscape/translations , which will be used to update the website and wiki once we are confident on the quality of the instructions for new translators.
They is still room for changes, depending on your feedback and remarks, so feel free to report if anything is not working as it should, or if you see anything that could be better automated, and I'll try to fix it.
** Automation **
- The potfile will now be updated /daily/ from the related branches, and the new strings should also be immediately available in Weblate. - Weblate should push changes to the translation repository /daily / - The Inkscape code (artifacts) will be updated /weekly/ from the translation repository - Documentation (man, tutorials, keys) are also present on weblate
** Weblate process **
Weblate supports a variety of workflows, and we should be able to accommodate them based on your needs. The current (default) state is "anyone can suggest translations, anyone /who is logged in/ can validate translations". We can create teams who would have review rights for languages if needed - see https://docs.weblate.org/en/latest/admin/access.html for what is doable. Weblate logins are through gitlab, so that we (ideally) don't have to deal with spam accounts (and any string change will be tied to a gitlab user).
Weblate lets people download and upload po files, and supports things like "upload po files as a set of suggestions to review", so any current workflow based on poedit or other tools that you would already use should still work.
If you have any question, please reach out, either in the ML, or in the channel, or in an issue in https://gitlab.com/inkscape/translations/-/issues
And thanks to Maren for the early feedback on the setup!
Best,