A translation workflow for an Addon

International
1

Just added a Translation for Polish to my bespoke Role Reversal rule addon. (It was the native tongue of the original requestor.)

The workflow feels as though it has too many steps. (Claude might have to build a dedicated Addon Translator tool to make a streamlined workflow! Possibly with a functionality to leverage Weblate before letting the AI join the party.)

Here is the workflow after installing the experimental Addon Pack and Ship utilities tool:

  1. Select the addon to be translated in the Tools → Utilities → Addon Pack and Ship.
  2. Click the Compile Translations (which rebuilds the “po/template.pot” of translatable strings in your local addon’s plugins folder)
  3. clicked the hotlink for the selected addon to open its local plugins folder
  4. Open the po subfolder
  5. copy the template.pot to an AI. (I used Claude using the sonnet model in a firefox browser window and prompted: Please make a Polish translation file.)
  6. Prompted the AI to create a translation for the target language.
  7. copy that new <language code>-local.po (e.g. pl-local.po for Polish) back to the local addon’s po subfolder
  8. edit the <language code>-local.po to fix any “my hovercraft is full of eels” problems.
  9. Click the Compile Translations again (to build the RoleReversal/locale/pl/LC_MESSAGES/addon.mo used by the GUI)
  10. restart Gramps (in the target language) and verify the Addon translation worked and is correct
  11. fix any mistranslations (go back to to step 8)
  12. send the <language code>-local.po to the developer (submitting a PR against the GitHub repo for the addon is preferred)

Claude’s response

Please make a Polish translation file

References: