You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The UI ships in English, Spanish, German, and French. Portuguese is the next most-requested language family and the infra already supports adding one.
Scope
Follow the existing pattern exactly: src/locales/pt/translation.json mirroring the key structure of src/locales/en/translation.json, plus the import and LANGUAGES entry in src/i18n.ts.
Translate naturally (pt-PT or pt-BR, say which in the PR). If you're not a native speaker, please say so — machine-translated catalogs will be reviewed, not merged blind.
Acceptance criteria
All keys present — the i18n token-parity tests (src/lib/i18n.test.ts) pass.
npm test green; no other source files touched.
Portuguese appears in the in-app language switcher.
Status in 89f65c8: a machine-drafted pt catalog (src/locales/pt/translation.json) is registered and key-parity tested. Leaving this open until a native Portuguese speaker reviews the copy. Contributions welcome.
Copy-review pass opened in #27. It keeps the catalog pt-BR and fixes the substantive defects in the machine draft:
Redaction → "Redigir" was wrong (that means "to write/draft" in Portuguese) — now "Tarjar"/"tarja" across the tool label, shortcut, help, export note and the failure/verification toasts.
Flip labels said "Inverter H/V" while their tooltips said "Espelhar" — unified.
AcroForm kinds "Marcação"/"Opção" were ambiguous — now "Caixa"/"Botão de opção".
Grammar/anglicism cleanups ("escalar" → "redimensionar", "gravados" → "incorporados", comma splice in the privacy note, and a few awkward phrasings).
Key parity holds (378 keys), npm test 88/88, typecheck and consistency check clean, one file touched. Still AI-assisted, not a native read — #27 deliberately does not auto-close this issue, since the native-speaker review you asked for is the remaining step.
The catalog ships pt-BR and the copy-review pass fixed the substantive defects in the machine draft: redaction renamed from the wrong "Redigir" (to write/draft) to "/tarjar"/"tarja", flip labels aligned with their tooltips, AcroForm kinds disambiguated, and grammar/anglicisms corrected.
Verified on the merged commit: key parity 378/378 against English, npm test 88/88, typecheck clean, build:pages green. One file changed; no dependency or test changes.
One caveat recorded honestly: this review was AI-assisted, not a native speaker's. The copy is now internally consistent pt-BR, but a native read is still welcome as a follow-up issue if you want the extra polish.
Activity
Kayforkind commentedon Oct 9, 2026
Status in 89f65c8: a machine-drafted pt catalog (src/locales/pt/translation.json) is registered and key-parity tested. Leaving this open until a native Portuguese speaker reviews the copy. Contributions welcome.
Kayforkind commentedon Oct 31, 2026
Copy-review pass opened in #27. It keeps the catalog pt-BR and fixes the substantive defects in the machine draft:
Key parity holds (378 keys),
npm test88/88, typecheck and consistency check clean, one file touched. Still AI-assisted, not a native read — #27 deliberately does not auto-close this issue, since the native-speaker review you asked for is the remaining step.Fix Portuguese redaction terminology in the pt catalog
Kayforkind commentedon Oct 31, 2026
Closed by #27, merged to
mainas 578c55b.The catalog ships pt-BR and the copy-review pass fixed the substantive defects in the machine draft: redaction renamed from the wrong "Redigir" (to write/draft) to "/tarjar"/"tarja", flip labels aligned with their tooltips, AcroForm kinds disambiguated, and grammar/anglicisms corrected.
Verified on the merged commit: key parity 378/378 against English,
npm test88/88, typecheck clean,build:pagesgreen. One file changed; no dependency or test changes.One caveat recorded honestly: this review was AI-assisted, not a native speaker's. The copy is now internally consistent pt-BR, but a native read is still welcome as a follow-up issue if you want the extra polish.