ci: sync stable branch translations

[susnux]

☑️ Resolves

Only main branch will be localized by Transifex.
To also update the stable branch with translations we need to synchronize them.

This actions does following:

• clone both branches
• combine po files from both branches for each language
• check the stable branch po template which messages are needed
• copy needed messaged from the combined po file (use the main if the translation differ)

This works locally, but I am not sure if the msgcat and msgmerge commands are installed on the runner.

🏁 Checklist

• ⛑️ Tests are included or are not applicable
• 📘 Component documentation has been extended, updated or is not applicable
• 2️⃣ Backport to stable8 for maintained Vue 2 version or not applicable

[ShGKme]

To also update the stable branch with translations we need to synchronize them

Isn't it supposed to be covered by the bot (.tx/backports file)?

[susnux]

Isn't it supposed to be covered by the bot (.tx/backports file)?

I did not find any information on this 🤔

[ShGKme]

I mean this:
https://docs.nextcloud.com/server/latest/developer_manual/app_development/translation_setup.html#branch-selection-tx-backport

[susnux]

I mean this: https://docs.nextcloud.com/server/latest/developer_manual/app_development/translation_setup.html#branch-selection-tx-backport

But this is only for apps, we do not use the app translations but the native transifex integration

[nickvergessen]

But this is only for apps, we do not use the app translations but the native transifex integration

That's correct, and iirc, the sync simply has a branch list on the config, but i never tried it.

[susnux]

@nickvergessen yes you can add branches for Transifex, but if I understood that correctly it will create new resources for translators. That is not what we want - no?
Because in this specific case we want to sync main to stable8 as in theory they should have the same strings (stable 8 is just the Vue 2 version of main - feature wise and thus string wise (code wise there are more changes)).

[ShGKme]

But this is only for apps, we do not use the app translations but the native transifex integration

Does it mean we need it globally in nextcloud-libraries/.github as it is not nextcloud/vue specific proble?

[nickvergessen]

We barely add and remove language strings here, so I think for now I will test if simply adding the branch works and does not create a new resource, we'll do that or manually copy the language files one time afterwards

[susnux]

Does it mean we need it globally in nextcloud-libraries/.github as it is not nextcloud/vue specific proble?

How many libraries use translations?
And then how many libraries use translations and have multiple supported branches?

[ShGKme]

How many libraries use translations?

At least 4

And then how many libraries use translations and have multiple supported branches?

At least 2

[nickvergessen]

Unless there is immediate need to fix this due to customer demand, please let this sit until after my vacation, so we can first try if it works with transifex directly.

[nickvergessen]

So after checking it seems the inline feature of Transifex is focusing on feature Pull requests, not on "stable branches". So copying them to/from main sounds like the best idea. Whether we need to merge them or not is another question. We can give translation folders instead of files, so each branch could have their own files:
https://help.transifex.com/en/articles/6265125-github-installation-and-configuration#h_b827747da8

So we could have a cron action that copies the PO files from stable to main and the POT from main to the stables?