i18n-localization

Run the i18n checker script against your project path to scan JSX and TSX files for text directly embedded in elements, attributes like title and placeholder, and button or heading content. Files already using t() or useTranslation are excluded from hardcoded-string flags.

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

react-i18next uses the useTranslation hook with t('key') calls and works across React frameworks. next-intl provides useTranslations scoped to namespaces and integrates with Next.js App Router conventions. Both patterns are recognized by the checker.

Yes, it scans Python files for hardcoded strings in print statements, raised exceptions, and Flask flash messages. It recognizes gettext patterns like _('key') and gettext() calls as proper internationalization usage.

RTL breakage usually comes from physical CSS properties like margin-left and padding-right that do not flip direction. Use logical properties such as margin-inline-start and padding-inline-end, and mirror directional icons with a scaleX transform under [dir="rtl"].

Regex-based detection can produce false positives on capitalized text that is not user-facing and may miss dynamically constructed strings. The checker limits analysis to 50 files and skips test, build, and dependency directories.