// Add or update a language translation in the privacy policy generator. Trigger when user says: "add {language} translation", "add locale", "translate to {language}", "add localization for {language}", or when a user wants to contribute a new language.
| name | add-localization |
| description | Add or update a language translation in the privacy policy generator. Trigger when user says: "add {language} translation", "add locale", "translate to {language}", "add localization for {language}", or when a user wants to contribute a new language. |
cp src/locales/en.json src/locales/{code}.json
Use the ISO 639-1 language code (e.g., es, fr, de, ja, pt, zh).
Edit the new JSON file. Only translate values, never keys.
✅ Correct:
"wizard.step1.tagline": "Genera un documento personalizado..."
❌ Wrong — don't change keys:
"wizard.step1.tagline_es": "Genera un documento personalizado..."
{{ variable }} placeholdersKeep placeholders like {{ appName }}, {{ platformDesc }}, {{ deviceType }} unchanged in the translated text.
In src/js/localeMixin.js, add to availableLocales:
availableLocales: [
{ code: 'en', label: 'English' },
{ code: '{code}', label: '{Native language name}' }
]
Update the locale loop in render.sh to include the new language:
for lang in en {code}; do
echo "window.__locale = $(cat src/locales/$lang.json);" > "$LOCALE_JS_FILE"
done
npm run build
Open public/index.html — the language switcher dropdown now includes the new language.
{{ variable }} placeholders preservednpm run build succeedsthirdpartyservices.yml — only the name field in the locale JSON if you add locale-specific names.meta.* keys) are updated dynamically via JS after page load.