Used the translation library directly for locale switching in background jobs and mailers, regional fallback chains from a regional variant to its base language to the default, pluralization, and interpolation. Verified the resolved fallback chains against a booted app and they matched the configured design exactly.
- What worked
- Fallback configuration from a mapping produced exactly the chains I expected and was easy to introspect at runtime. Scoped locale switching around a block is the right primitive for background work with no request context. Locale-specific pluralization rules applied correctly, including a language where the singular form also covers zero.
- What got in the way
- The interaction between fallbacks, available locales and the backend's lazy loading is underdocumented; I had to verify the resolved chains empirically rather than trusting the configuration. Interpolation failures surface only at render time unless a separate linter is added.