Translating this repo: What you need to know as maintainers
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 1/5
- Tiempo estimado
- Menos de una hora
- Aptitud para principiantes
- 90/100
- Tipo de issue
- Documentación
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Área
- documentation
Línea de trabajo
Lea el issue para comprender el proceso de traducción del repositorio problem-specifications. El issue explica los nuevos repositorios (i18n, translator), los scripts y el flujo de trabajo para traducir contenido nuevo. Como mantenedor, debe saber cuándo aplicar la etiqueta 'ready-to-translate' a los PR. No se requieren cambios de código; esto es puramente informativo para los mantenedores.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Hi maintainers!
We'll soon be launching Exercism in multiple languages. This issue explains how the translation process works. I'm opening a variant of this issue around GitHub, so apologies if you see it multiple times. If there are any docs that you think need updating for this (either within tracks, or globally), please PR changes :)
New bits
There are two new repos to be aware of:
- i18n: This is where the translations live
- translator: This is the machinery behind the translations
There are also some new scripts that will be coming from org-wide-files, which will be PR'd and auto-merged soon (for non-track repos, these will be added directly to the repo)
I am manually generating translations of all content in this repo, so all you need to consider is new changes.
Methodology for new content
When a PR opens, a script will check whether the new git blobs exist in the i18n repo for all locales. If they don't, the PR will fail CI.
You (a maintainer) can add a new label ready-to-translate to the PR, which will open a new issue in the i18n repo with details. That new issue then triggers a workflow that causes the files to be translated and pushed to the i18n repo. Once that happens, the PR in this repo will have its check re-triggered and it should go green, at which point you can merge. For most situations this whole thing should take ~10 minutes end-to-end.
If someone pushes more copy changes to the PR, the label will automatically be removed and you will need to add it again to retranslate. So I recommend only adding the label once the PR is signed off to avoid churn. Each translation also costs us money, so this approach also saves us real cash!
A PR with more than 3,000 untranslated words gets held for manual approval. Please ping me if you hit this.
Existing Pull Requests
Any PRs that predate this will need action before they can be merged. Any of the following will run the relevant i18n GitHub Action:
- "Update Branch" button if available
- Rebasing/pushing to the PR
- Closing/Reopening the PR
If the PR changes English, add the ready-to-translate label once the check has run.
What's translated?
On a track, these files are treated as English and get translated:
exercises/*/*/.docs/instructions.mdexercises/*/*/.docs/instructions.append.mdexercises/*/*/.docs/introduction.mdexercises/*/*/.docs/introduction.append.mdexercises/*/*/.docs/hints.mdexercises/shared/.docs/*.md(help, tests, debug)concepts/*/about.mdconcepts/*/introduction.mddocs/*.md(the track's own documentation pages)
Plus a few text fields, rather than whole files:
- Exercise and concept names from
config.json - Exercise and concept blurbs from each exercise's or concept's
.meta/config.json - Track doc titles and blurbs from
docs/config.json
Everything else in the repository is left along. Nothing is ever written to track repositiories. The workflows only read a PR, and the translations are stored in exercism/i18n.
Viewing Translations
There are indexes for each language/repo here at https://github.com/exercism/i18n/blob/main/index/markdown/$LOCALE/$REPO.md where you can get links to all the translations. For example: Hungarian Python.
(Fixes to translations will happen via the forum, but I think that's a different discussion from this issue as it's org-wide and not your (direct!) responsibility as maintainers so I don't want to burden you with more information).
I intend to push Hungarian live today, and then start rolling other (natural) languages out over the next week.
- Lenguaje dominante
- Ruby
- Estrellas
- 362
- Forks
- 566
- Merge medio
- 15 h 13 min
- PR fusionados (30 d)
- 8
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de exercism/problem-specifications
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
exercism/problem-specifications#2704 · 21 comentarios · 8 reacciones ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 35/100
exercism/problem-specifications#2153 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
exercism/problem-specifications#2120 · 7 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
exercism/problem-specifications#2108 · 1 comentario · 5 reacciones ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
exercism/problem-specifications#2083 ·
Los mantenedores suelen responder en 1 día
Todos los issues de exercism/problem-specifications
Issues similares
-
開発用DockerイメージにPlaywrightのシステム依存を追加するPosiblemente ocupada @momocus la tomó hoy. Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
sakazuki-org/sakazuki#1453 ·
Los mantenedores suelen responder en 3 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
jenkins-infra/jenkins.io#9615 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
fix(ocr): compile the Tesseract-free pipeline with Tokio runtimePosiblemente ocupada @Goldziher la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Metric tooltips that contradict how the metric is calculatedPosiblemente ocupada @aniadeadu la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
WikiEducationFoundation/WikiEduDashboard#7303 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
WhatsApp Cloud template sync saves a partial template list when one page of the Graph API response failsPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 2 días