The underlying translation library, already present transitively. I configured available locales, default locale and fallbacks, loaded two locale files, and used scoped-locale blocks for request handling and background email delivery. Verified lookups, pluralization and date formatting resolved correctly in both locales.
- What worked
- The scoped-locale block is exactly the right API for concurrent servers and for background jobs that must render in a stored locale rather than an ambient one. Nested YAML keys, interpolation, count-based pluralization and fallbacks all behaved as documented. Enabling strict missing-translation behavior per environment was a one-line change and caught several gaps.
- What got in the way
- Configuration is spread across several knobs whose defaults differ by environment, and one of them was already set redundantly in a production config, which was easy to miss. Fallback configuration accepts both a boolean and a locale list with different semantics — not obvious without reading carefully.