Skip to content

feat(i18n): add Spanish - #344

Open
PedroFlores199 wants to merge 1 commit into
MehdiMamas:mainfrom
PedroFlores199:feat/es-locale
Open

PedroFlores199 wants to merge 1 commit into
MehdiMamas:mainfrom
PedroFlores199:feat/es-locale

Conversation

@PedroFlores199

Copy link
Copy Markdown

What this changes

Adds an es catalog (Spanish, Spain) and registers it in the language picker. It has all 439 keys of en, with the same $N slots and untouched placeholders blocks.

  • _locales/es/messages.json: new catalog, 439 strings
  • src/i18n/runtime.js: import, CATALOGS and LOCALE_NAMES ("Español")
  • docs/translating.md: Apple's Spanish name for the Passwords app and a row in the language table
  • test-harness/automation/i18n.test.ts: Spanish checks for es/es-ES/es-419 resolution, $N slots, ¡/¿ punctuation, the unlock code wording, Apple's names and the 132-character description; frameError ("Error: $1") is spelled the same as in English, so it joins SAME_AS_EN

Terminology follows Apple's Spanish UI: "Contraseñas de iCloud", "la app Contraseñas", "iCloud para Windows", "llaves de acceso" (passkeys), "código de verificación", "clave de configuración" (setup key). The pairing PIN is always "código de desbloqueo", never the verification code. "Login" is "inicio de sesión", as in Bitwarden's Spanish UI, and the copy uses the informal "tú".

Why

Refs #265: Spanish as a new interface language. A browser set to Spanish gets the English UI today.

How I checked it

  • pnpm typecheck
  • pnpm test
  • node scripts/check-locales.ts and node test-harness/automation/i18n.test.ts pass with the new Spanish checks
  • Browser tests, if autofill, the menu or the helper protocol changed
  • Docs (README, SETUP, AGENTS) updated if how something works changed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant