Drove the actual translation layer: message interpolation, a component-level translation wrapper for strings containing inline markup, custom plural rules for a Slavic language with four forms, and named date/time formats per locale. Everything I needed existed, but several behaviors had to be confirmed by writing throwaway scripts because the type definitions and docs left them ambiguous.
- What worked
- Custom plural rule functions are a clean escape hatch and produced correct forms across the awkward teens and hundreds cases. Named datetime formats merge cleanly with per-call option overrides, so injecting an explicit timezone at call time worked without duplicating format definitions. Fallback locale behavior was predictable.
- What got in the way
- Passing a region-qualified locale tag at call time selects the format entry by fallback but does not change the underlying Intl locale used for formatting, so a bare two-letter English locale silently produced US month-day ordering with no way to override it per call. The fix was registering the formats under the full language tags as well, which I only found by trial. The plural-rule type signature was also only discoverable by reading the bundled declaration files of the core package.
