Module release process - adding translations to module

Omeka S Development
1

From Translate Omeka S - Omeka S User Manual and Internationalization - Omeka S Developer Documentation I can’t determine what needs to be done to add strings and their translations to a existing Omeka S module.

With an existing module like GitHub - omeka-s-modules/NdeTermennetwerk: Adds NDE (Netwerk Digitaal Erfgoed) Termennetwerk to the Value Suggest module, if I add code with // @translate decorations what do I have to do get these new strings into Transifex ? Or can I just update the template.pot and *.po files? Do I need to run Gulp tasks (if yes, where are they located)?

The latter solution can be done in a single pull request. If there’s a Transifex step needed, than how to proceed, do the pull request with mention of new translatable string (so someone - like @jimsafley - can update the strings in Transifex so they can be translated by others) and prior to the merge , someone updates the *.po and *.mo files?

2

Before release we run the following:

$ npx gulp i18n:module:template
$ tx push -s
$ tx pull -a -f
$ npx gulp i18n:module:compile

i18n:module:template updates the translation template for the module. push pushes source files to transifex. pull pulls translations for all languages from Transifex. i18n:module:compile builds translation files for the module. We try to put some time between push and pull.

Pretty sure only we can use tx for translations in our Transifex organization.