Translations Missing After i18n Changes
After Cursor reorganized your internationalization (i18n) files, translations are no longer working. Pages display key names instead of translated text, or missing locale files cause errors.
i18n configuration or translation file paths were broken during refactoring.
Error Messages You Might See
Common Causes
- Translation file paths changed, not pointing to actual files
- Locale not initialized or set correctly
- Translation keys changed, but not all places updated
- Language JSON file is malformed
- i18n library configuration broken after refactor
How to Fix It
Verify translation paths in config. Check locale JSON syntax: {"key": "value"}. Initialize i18n before app renders. Use consistent key names across files. Log detected locale and loaded files for debugging.
Real developers can help you.
You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.
Get HelpFrequently Asked Questions
How do I add a new language?
Create locale file (en.json, es.json). Add to i18n config. Test by changing language in app.
How do I handle missing translations?
Set fallback language (usually English). Show key name if translation missing. Log warnings.