TBv3: Spanish and Chinese lack about a third of the UI strings

Abierto
  • ¿Algo no está bien?
#2,918 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Área
internationalization

Línea de trabajo

Read the TBv3 translation catalogs and compare the Spanish and Chinese keys with the English catalog; the issue names the affected groups as repo, common, import, reference, cloneToSource and addToCollection. Fill every missing es and zh key with machine-translated drafts, mark them for native-speaker review, and explain the marking in the PR. Done means all English keys are present in es and zh; pt-BR is explicitly out of scope.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

component/web decision/human-review signal/low-risk signal/needs-human stage/triaged type/feature

Decided (Jon, Oct 26): machine-translated drafts for es and zh

Fill every missing es and zh key with a machine-translated draft now, so users see far less English. A native speaker reviews them later. Mark the drafts so that review can find them, and say how in the PR. pt-BR's 11 missing keys are left to its maintainer and aren't part of this change.

TBv3 offers Spanish and Chinese, but on main (e0baf875) es lacks 430 of the 1,055 English keys (41%) and zh lacks 360 (34%). Those strings show in English. Most of the gaps are in repo (es 172, zh 140), common (87, 59), import (43, 43), reference, cloneToSource and addToCollection. Those are mostly features added after the catalogs were last filled in. pt-BR lacks 11.

The weekly i18n check (private for now: ocl_online#523) records these gaps as known and fails on any new one, so the gap can't grow while this is open.

  • Decide how to fill them: a machine-translated draft reviewed by a native speaker, or hiding es and zh from the language menu until they're done.
  • es, zh and pt-BR have every English key.
Lenguaje dominante
Sin datos de lenguaje
Estrellas
4
Forks
2
Merge medio
2 h 12 min
PR fusionados (30 d)
1

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OpenConceptLab/ocl_issues

Todos los issues de OpenConceptLab/ocl_issues

Issues similares

Más issues de Internationalization

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.