translate

To translate missing i18n strings, compare the source `_locales/en/messages.json` against each target locale's `messages.json` and automatically fill in the untranslated gaps. The process detects missing keys, translates them, and preserves existing formatting to maintain localization consistency across browser extensions.

Chrome extension i18n translation strictly preserves placeholders and HTML tags found in the original messages.json strings. It also keeps the English `description` field unchanged and ensures the output JSON remains valid while matching the English key order.

The best way to find untranslated or orphan keys is by comparing `_locales/en/messages.json` to each `_locales/<lang>/messages.json`. This localization check reports missing, untranslated, and orphan keys so you can safely update target files and remove obsolete translations.

Yes, you can sync German `de` and `de_DE` locale messages.json files during browser extension translation. The workflow enforces synchronization between the two German locale variants, ensuring both files contain identical translated i18n strings and key ordering.

You can automatically reorder JSON keys in `_locales` by using the English `messages.json` as the structural source of truth. The localization process aligns the key order in every target language file to match the English baseline while validating JSON correctness.

Translated messages.json files fail JSON validation when structural integrity is broken during string insertion. The translation workflow prevents this by validating output JSON correctness after writing, ensuring placeholder syntax and HTML tags remain intact and syntactically valid.