i18n-validate

To check for missing translations across multilingual locale files, validate your locale assets to identify gaps, orphaned keys, and placeholder inconsistencies. This generates a structured JSON report with a per-language completion breakdown and actionable recommendations for pre-release QA.

You can validate i18n glossary mismatches and placeholder consistency within CI workflows by running pre-merge checks on your locale files. This enforces JSON syntax validity, glossary alignment, and length budgets, producing structured output suitable for blocking invalid pull requests.

Detecting orphaned keys in multilingual JSON locale files involves scanning your locale directories to find entries present in some languages but missing in others. This process highlights unused or incomplete translations across specified locales like en, fr, de, and es.

i18n validation enforces length budgets and JSON syntax validity by checking translation assets against defined constraints before release. It identifies syntax errors and over-limit strings across your locales, ensuring UI text quality and preventing layout breaks in deployed applications.

To get a per-language completion breakdown for your translation files, run a validation check across your locale assets. This produces a structured JSON output detailing the completion percentage and specific gaps for each language, giving you actionable pre-release recommendations.

Automated translation validation for pre-release QA focuses on structural completeness, syntax validity, and glossary alignment, but does not assess linguistic quality, cultural nuance, or contextual flow of the translated text across your supported locales.