add-localization

To add a language translation, you create a locale JSON file from the English source, translate the string values, and register it in the availableLocales configuration. You must also update the render.sh build loop to ensure the app loads the new translations at runtime.

When translating a locale JSON file, you must keep dynamic placeholders like {{ appName }}, {{ platformDesc }}, and {{ deviceType }} completely unchanged. Leaving these variable placeholders untouched ensures the generated privacy policy remains accurate and properly populated.

Adding i18n locale support requires using standard ISO 639-1 language codes. For example, you would use 'es' for Spanish. Providing the correct two-letter code ensures the locale is properly registered for UI selection in the language dropdown.

To make a translated locale visible in the language dropdown, you must update the availableLocales list and the render.sh locale build loop. After registering the new language, run a successful npm run build to validate that the locale appears correctly in the UI.

Yes, this localization process applies to adding locales for legal templates, FAQ text, disclaimer text, and platform vocabulary across all supported app types. Creating and translating the locale JSON file ensures all UI and legal text is fully localized for the user.

If a privacy policy translation is not showing up, the locale JSON file may not be properly registered in the availableLocales list or the render.sh build loop. You must ensure a successful npm run build completes to validate visibility in the language dropdown.