feat(i18n): add Spanish (es) translation#292
Conversation
rmyndharis
left a comment
There was a problem hiding this comment.
Thanks for this, @fentinak — the registration in i18n/index.ts is wired correctly (import, supportedLanguages, languageOptions, and the resources map), and the translation reads naturally with all interpolation variables ({{count}}, {{name}}, …) and <Trans> tags preserved.
One blocker before merge: the branch predates a few locale additions on main, so es.json is missing 41 leaf keys that en.json now has — these would render as raw keys in the UI. Could you rebase on main and add them?
Missing:
- The entire
templates.*namespace (38 keys — the message-templates feature):nav.templates, the form labels/placeholders,templates.toasts.*,templates.empty.*,templates.actions.copyName, etc. common.showApiKey/common.hideApiKeymessageTester.notOnWhatsApp
A quick way to find the gaps is to compare the leaf-key paths of en.json and es.json. Once es.json is at parity with en.json, this is good to merge. Thanks again for contributing!
a1793be to
6bc215a
Compare
|
Done! I've rebased on main and added all 41 missing keys: the complete templates.* namespace, common.showApiKey / common.hideApiKey, and messageTester.notOnWhatsApp. [es.json] is now at full parity with [en.json]. Ready for review! |
Stale — the original blocker (41 missing locale keys) was resolved by the author's rebase to full en.json parity (486/486 keys verified). Dismissing so the completed Spanish translation can merge for v0.3.0.
Description
Adds a complete Spanish translation for the dashboard. All strings in [en.json] have been translated, and the language is registered in [index.ts]
Type of Change
Checklist
Screenshots (if applicable)
Related Issues
Closes #