Achieve 100% l10n completion for Telugu, Hindi, and Urdu (Phase 1)
Summary
Phase 1 requires 100% localization completion for three languages: Telugu (te), Hindi (hi), and Urdu (ur). Currently, English (en) is the reference language with ~2684 lines of translation keys.
Current Status
| Language | File | Lines | Status |
|---|---|---|---|
| English (en) | src/locales/en/translations.json |
2684 | Reference (complete) |
| Telugu (te) | src/locales/te/translations.json |
2421 | Incomplete — ~263 keys missing/empty |
| Hindi (hi) | src/locales/hi/translations.json |
2498 | Incomplete — ~186 keys missing/empty |
| Urdu (ur) | — | 0 | Not yet created |
Tasks
Phase 1 Languages
-
Telugu (te): Fill all missing/empty translation values to match en - Run
bun run i18n:scanto get an up-to-date key count - Identify all empty
""values and missing keys insrc/locales/te/translations.json - Translate all remaining keys
- Run
-
Hindi (hi): Fill all missing/empty translation values to match en - Identify all empty
""values and missing keys insrc/locales/hi/translations.json - Translate all remaining keys
- Identify all empty
-
Urdu (ur): Create new locale from scratch - Create
src/locales/ur/translations.json - Mirror the full English key structure
- Provide complete Urdu translations for all keys
- Register the locale in
src/i18n.ts
- Create
Quality Checks
-
Run bun run i18n:check— must pass with zero missing keys for all three languages -
Verify RTL layout support for Urdu (add dir="rtl"handling if needed) -
Spot-check translations in the app UI for all three languages -
Ensure no untranslated strings fall back to English in production
Notes
- Use
bun run i18n:scanto extract the latest translation keys - Use
bun run i18n:checkto verify completeness - All translations should be culturally appropriate and use standard terminology for healthcare/medical camp contexts