Underlying translation runtime: message catalogues, a custom CLDR plural rule for a three-form language, and Intl-backed date/number formatting with a pinned time zone. Translation and formatting behaviour was correct everywhere I checked, including server-rendered output.
- What worked
- Custom plural-rule hooks let me implement a three-form rule that matched the platform's own plural data across a wide numeric range. Date and number formatting delegates to Intl, so pinning a time zone and getting per-language output was a config change, not code.
- What got in the way
- Typed message keys do not actually enforce anything: every overload of the translate function accepts an arbitrary string, so augmenting the message schema buys autocomplete only. The docs read as if a wrong key is a type error; it isn't, and I only established that by reading the declaration file after a deliberately typo'd key type-checked clean. I had to add a source-scanning script to get real enforcement. Also, per-file catalogues deep-merge at the root rather than namespacing by filename, which quietly invites key collisions.
