There's no guide for translating OpenSignup, and no Swedish glossary

Abierto
  • ¿Algo no está bien?
#637 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
59/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
documentation, internationalization

Línea de trabajo

Start with the translation catalogs in src/messages/, inspect their namespaces and ICU examples, then check how SHIPPED and the completeness check from #623 work. Write docs/translating.md with the requested guide and Swedish glossary, link it from CONTRIBUTING.md, and run pnpm lint; it is done when the guide matches the catalog behavior and the lint command passes. This issue is explicitly planned after #623.

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

Descripción

enhancement pipeline:proposed

Needs your OK: this adds docs/translating.md, a guide for translators, with a Swedish glossary for your reviewer to settle. Swap pipeline:proposed for pipeline:ready to have it built.

What happens

Nothing tells a contributor how to add a language, how to write ICU messages, or which Swedish words to use for OpenSignup's own terms. Without a glossary, the same thing ends up with three different names across the app and the emails.

Fix, in outline

  • docs/translating.md, covering:
    • how the catalogs work (src/messages/, namespaces by audience);
    • ICU plural, select and tags, with examples from the catalog;
    • how SHIPPED and the completeness check (#623) decide when a language can be chosen;
    • how to add a language;
    • that a language ships only after a native speaker reviews it in context, from screenshots and rendered emails, not just the JSON.
  • A Swedish glossary, for the reviewer to settle before the translation starts. It covers signup, slot, spot, organizer, participant, sign up, cancel and reminder; the tone (du, not ni); and the date and time style ("lör 3 maj", "18:30").
  • A link from CONTRIBUTING.md.

Choices this makes

  • Starting terms, for the reviewer to accept or change: anmälningslista (signup), pass or tid (slot), plats (spot), arrangör (organizer), deltagare (participant). Default: these, until the reviewer decides.

Order

After #623, because the guide describes its checks.

Done when

  • The guide exists, is linked from CONTRIBUTING.md, and matches how the catalog check and SHIPPED work.
  • pnpm lint passes.

Planned with the owner in https://claude.ai/code/session_01EFKmj716ZY3b3SwR8TV8Y2 and checked against the code on main at 35288fa. The full plan is private to the owner's account: https://claude.ai/artifact/VgQH6U2s2EVx3LX991fJi8 (a Claude session on that account can open it with the Artifact tool's read action). This is step 1.8 there.

Lenguaje dominante
TypeScript
Estrellas
19
Forks
4
Merge medio
19 h 46 min
PR fusionados (30 d)
194

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 richshaw/OpenSignup

Todos los issues de richshaw/OpenSignup

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.