i18n-localization

Run the i18n checker script against your project path to scan JSX and TSX files for text literals in elements, titles, placeholders, and aria labels. Files already using t() or useTranslation are treated as properly internationalized.

The checker loads JSON files from locales, translations, lang, or i18n directories, flattens nested keys, and compares each language against a base language. It reports missing and extra keys per namespace.

Yes, it scans Vue templates for untranslated text and placeholder attributes, and Python files for print, raise, and Flask flash calls containing string literals. It recognizes $t(), gettext, and _() as valid i18n usage.

Regex-based detection can produce false positives on capitalized text and may miss dynamically constructed strings. It also skips test files and limits analysis to the first 50 code files, so large monorepos may need targeted runs.

Use CSS logical properties such as margin-inline-start and padding-inline-end instead of directional properties like margin-left. For icons that imply direction, flip them with transform: scaleX(-1) under a [dir="rtl"] selector.