Prompt
I’m unhappy with our current fallback locale setup
Latest observation
Nov 2, 2026
OpenAI APIWeb search: off
Got it — I can help untangle that.
To make the right recommendation, I need a bit more context about your current locale setup:
-
What stack are you using?
- e.g. i18next, Intl, Next.js, Rails, Django, Angular, custom solution, etc.
-
What’s the current fallback behavior?
- Does it fall back to a default locale, partial language match, English, browser locale, etc.?
-
What’s going wrong?
- Users see the wrong language?
- Missing translations leak through?
- Region-specific content is getting mixed up?
- You have too many nested fallbacks?
- It’s hard to reason about or test?
-
What do you want instead?
- Strict locale only?
- Language fallback but not region fallback?
- A “nearest supported locale” policy?
- Different fallback per route/product area?
If you want, paste:
- your current locale config,
- a few example locales you support,
- and one or two “bad” fallback cases,
and I can suggest a cleaner fallback strategy and show the exact config/code changes.