Open hasecilu opened 4 months ago
Before merging maybe some other notes/comments should be added to the script to make maintainer or translator aware of someting.
Right suggestion. :grinning: I can add a few words about your script here in this repository. Now I will say that It is ro recommended solution by me :cactus: for both translators and developers of external workbenches. :1st_place_medal:
The previous script was made in my workflow as translator: update, translate, release.
With the new integration of external WB to Crowdin a new task is needed for maintainer so I made some changes.
-U
flag for maintainer to update only main agnostic file-R
flag for maintainer to release all translations-r
& -u
for translators to do the things they could do beforeDescription:
Create, update and release translation files.
Usage:
./update_translation.sh [-R] [-U] [-r <locale>] [-u <locale>]
Flags:
-R
Release all locales
-U
Update main translation file (locale agnostic)
-r <locale>
Release the specified locale
-u <locale>
Update strings for the specified locale
Maybe some links to some resources could be added?
The workbench must mark the strings with
translate()
orQT_TRANSLATE_NOOP()
on Python files.Before merging maybe some other notes/comments should be added to the script to make maintainer or translator aware of someting. Maybe links to https://freecad.github.io/DevelopersHandbook/technical/translation.html or https://wiki.freecad.org/Translating_an_external_workbench?
This is already used on: