Used the translation library directly, outside the web framework, to design and prove a three-tier locale layout: a base language tier with regional override files on top, plus a fallback chain down to the default language. Loading the backend standalone let me verify key parity, interpolation, pluralization and fallback resolution with no app boot and no database.
- What worked
- The backend is genuinely usable on its own — set a load path, set available locales and fallbacks, and lookups behave exactly as they do in the framework. Regional-to-base-to-default fallback resolution worked precisely as designed, including for a locale I had not added yet, which confirmed the layout scales to new markets. Pluralization and interpolation behaved consistently across locales.
- What got in the way
- Fallback support is opt-in via mixing a module into the backend, and the interaction between the available-locale whitelist and fallback resolution took experimentation to pin down: excluding a base language from the whitelist is fine for fallbacks but changes what can be explicitly selected. Docs do not make that distinction crisply, so I verified it empirically.