Request translation sync for RoomVox

[Rikdekker]

Prologue

The Nextcloud community on Transifex produces the translations of your app. To this end, the app author undertakes to comply with the following requirements:

• The app must be available in the Nextcloud App Store. Should the app be removed from the store, the translation work on Transifex will be paused or the resource removed.
• The app author must create an account on Transifex and join the Nextcloud project. This makes it easier to respond to queries regarding the app’s strings.

👤 App repository

To be done by you

• Link to your repository: https://github.com/nextcloud/RoomVox

• If the app is not in the Nextcloud organisation — not applicable, RoomVox is in the nextcloud organisation

  • Invite nextcloud-bot with write permissions
  • Make sure all translated branches do not have branch protection enabled, see https://docs.nextcloud.com/server/latest/developer_manual/basics/front-end/l10n.html#setup-of-the-transifex-sync for more details

• Create file l10n/.gitkeep with empty content

• Add .l10nignore to exclude compiled JS files and thirdparty code, e.g. ignoring compiled javascript assets and composer PHP dependencies in the vendor/ directory:

  js/
  vendor/
  

• Create file .tx/config with the app id (roomvox) substituted 3 times:

  [main]
  host     = https://www.transifex.com
  lang_map = hu_HU: hu, nb_NO: nb, sk_SK: sk, th_TH: th, ja_JP: ja, bg_BG: bg, cs_CZ: cs, fi_FI: fi
  
  [o:nextcloud:p:nextcloud:r:roomvox]
  file_filter = translationfiles/<lang>/roomvox.po
  source_file = translationfiles/templates/roomvox.pot
  source_lang = en
  type        = PO

• ⚙️ Validate your repository and translation strings:

  bash translations/validateSyncSetup.sh nextcloud RoomVox

• Name of the Transifex user: rikdekker

  For details see https://nextcloud.com/translation/ .

App ID: roomvox

Source template is translationfiles/templates/roomvox.pot — 469 strings, extracted from both the Vue frontend and the PHP backend, validated with msgfmt --check. All frontend call sites use the literal t('roomvox', '…') form, so the extractor sees the complete set.

One thing you may want to decide: translationfiles/{de,fr,nl}/roomvox.po are seeded with the app's existing hand-made German, French and Dutch translations (361 of 469 strings each), so those languages don't start from zero. Happy to drop them if you'd rather the resource started empty.

🏗️ Sysadmin team

• 👀 Ensure access:

  • Nextcloud organisation repository: Add nextcloud-bot with admin permissions
  • Other repositories:
    • Ensure the invite was accepted
    • Ensure the app certificate is linked to the same repository/author https://github.com/nextcloud/app-certificate-requests

• ⚙️ Ensure repository setup and run initial source validation:

  bash translations/validateSyncSetup.sh Owner Repository

• 🧑‍💻 Run the first sync manually:

  ssh transifex-sync.nextcloud.com

  cd /srv/docker-ci
  docker run -v /srv/cronie-data/transifexrc:/root/.transifexrc \
    -v /srv/cronie-data/gpg:/gpg \
    -v /srv/cronie-data/ssh/id_rsa:/root/.ssh/id_rsa \
    --rm -i ghcr.io/nextcloud/continuous-integration-translations-app \
    AUTHOR APPID

• Transifex: New resource should appear

• GitHub: Check if there was a sync commit in the repository

  • If not, go to Transifex, translate some strings in a language you know and trigger the sync again with the docker command

• Transifex: On the resource go to Settings > Untick "Your translators can translate resource strings" > Save settings

• ➕ Add "Owner Repository", into https://github.com/nextcloud/docker-ci/edit/master/translations/config.json

  • Pull request:
  • Request review from rakekniven

🔣 Translation team

Currently done by rakekniven

• Transifex: Check quality of the English source strings
• Transifex: Check translation guidelines
• GitHub: Approve the above pull request (and merge it)
• Transifex: On the resource go to Settings > Delete the resource
• Forum: Add resource to wiki

🏗️ Sysadmin team

• GitHub: Ensure the above pull request is merged
• 📅 Enable the daily sync:

  ssh transifex-sync.nextcloud.com

  cd /srv/docker-ci
  git pull origin master

[Rikdekker]

No rush on this — I saw in #977 that new resources are on hold because translators cannot cope with the influx of strings, and that is entirely fair.

One thing that may be relevant when you get to it, since it makes this request different from a typical new resource: RoomVox is not arriving empty. It was translated by hand before moving to the POT workflow, and those translations come with it:

Language	Translated	Untranslated
German	359 / 467	108
French	359 / 467	108
Dutch	359 / 467	108

So for three languages it starts at 77% rather than 0%, and the remaining 108 strings are mostly the notification emails, which had no translatable strings at all until now. translationfiles/{de,fr,nl}/roomvox.po are in the repo and validate with msgfmt --check.

I mention it only because "flood of strings" is exactly the concern you raised, and this one adds fewer than it looks. Happy to wait for whatever organisational solution you land on — and equally happy to drop the seeded PO files if you would rather the resource started clean.

[Antreesy]

Hi, thanks for opening an issue! It will be checked after 24.08 or later

[Rikdekker]

Gentle ping — you mentioned this could be looked at after 24.08, so following up now that we're past that.

No urgency from my side, and I understand #977 is still the blocker. Just flagging that RoomVox is still waiting, and that the POT is up to date in the repo whenever the resource is created.

Happy to keep waiting — a note on whether the hold is expected to lift this quarter would be useful for planning, but nothing more than that.

[nickvergessen]

At the moment it's not planned to add further language resources until a discussion can take place with the translation crew at the contributor week. We will align on some requirements for the apps there.

From my POV since you vibe coded the app in the biggest parts already, you can also try to vibe code translations for now. Having the js and json files in the repo is enough for them to work, so it's not blocking a release or anything.

[Rikdekker]

Thanks for the clear answer — that's useful, and no problem waiting for the contributor week discussion.

Good to know the js/json files are sufficient in the meantime; that matches how we've set things up, so nothing is blocked on our side.

One thing that would help: if the requirements you land on get written down somewhere public, a pointer would be appreciated. Happy to make sure the app meets them before this gets picked up again, rather than adding work for you later.

[Rikdekker]

Understood, thanks — I'll work with that.

On the translations: I've now completed Dutch myself (467/467), following the Nextcloud translation guidelines — sentence case, … for ellipsis, and consistent terminology within the resource. Dutch I'm happy to keep maintaining, and I can manage a couple of other languages.

German and French I've deliberately left at 359/467 rather than machine-translating them. I can't judge the quality there, and filling them in would mean they arrive as "already translated" and drop straight out of the translation queue — worse, I think, than leaving the gaps visible.

That's the part I can't solve on my own. Offering the app in every language it could reasonably support isn't something I can write myself, and beyond raw coverage the community side is what I'm actually after: native speakers catching nuances, reviewing what's there, and being able to correct it directly instead of filing an issue and waiting for me.

So longer term I'd like our apps on Transifex generally — IntraVox and IntroVox are already set up (#951, #938), FormVox has a request open (#989), and MetaVox would be the next one I'd ask for. No expectations on timing; I'd just rather say plainly where we're heading than open requests one at a time without context. Happy to align with whatever requirements come out of the contributor week.