Translation request for DashLink

Aperta
  • Qualcosa non va?
#1,014 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
20/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
bash, docker, json
Ambito
ci-cd

Direzione di ricerca

The sysadmin steps require editing translations/config.json to add "LexioJ dashlink", and running the docker sync on the transifex-sync server. Start from the unchecked '# 🏗️ Sysadmin team' boxes and the translations/validateSyncSetup.sh script. Done means the PR is merged and daily sync enabled via git pull on the server.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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/LexioJ/dashlink

  • If the app is not in the Nextcloud organisation

  • 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 following content, replace {{APPID}} with your app id 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:dashlink]
file_filter = translationfiles/<lang>/dashlink.po
source_file = translationfiles/templates/dashlink.pot
source_lang = en
type        = PO

  • ⚙️ Validate your repository and translation strings:

    bash translations/validateSyncSetup.sh LexioJ dashlink

    Validation passes on main (only remaining note is the missing l10n/de.json, expected before the first sync).

  • Name of the Transifex user: lexioj

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

Additional info:

🏗️ Sysadmin team

  • 👀 Ensure access:

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

    bash translations/validateSyncSetup.sh LexioJ dashlink

  • 🧑‍💻 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 \
  LexioJ dashlink

  • 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 "LexioJ dashlink", 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
Lingua principale
Perl
Stelle
47
Fork
38
Merge medio
2g 1h
PR unite (30g)
5

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nextcloud/docker-ci

Tutte le issue di nextcloud/docker-ci

Issue simili

Altre issue su Perl

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.