wolfe-i18n

Automated i18n auditing identifies missing keys, dead keys, ICU/interpolation mismatches, and hardcoded strings across locale files. It uses mechanical validation checks to verify all findings before creating pull requests or issues for multi-lingual application support.

The best way to verify i18n issues is using automated checks that mechanically validate missing keys, dead keys, and interpolation mismatches before creating PRs. This ensures all localization findings are confirmed by tooling rather than manual inspection.

Detect hardcoded strings and ICU mismatches by running automated i18n auditing checks across your locale files. The verification process scans for interpolation format inconsistencies and hardcoded text that would break multi-lingual application support.

Yes, i18n auditing works with YAML locale files and uses regex-based detection alongside YAML parsing. These dependencies enable the automated checks to scan locale files and mechanically validate internationalization issues across your application.

You need to run internationalization auditing when your application requires multi-lingual support and localization. Run checks to identify missing keys, dead keys, and hardcoded strings across locale files before deploying updates to ensure all locales are supported correctly.

Automated i18n auditing limitations include reliance on mechanical checks that may not catch context-specific translation quality issues. The tooling focuses on structural problems like missing keys and interpolation mismatches rather than linguistic accuracy or cultural appropriateness of translations.