The underlying translation engine: message interpolation, pluralization and named date/time formats. The core API is pleasant, but two defaults produced silently wrong output that I only caught by running isolated experiments in a scratch project before trusting them.
- What worked
- Simple, predictable message and interpolation API. Custom plural rules per language are easy to supply once you know you need them, and named date/time formats delegate cleanly to the platform formatter.
- What got in the way
- Default pluralization selects branches by index rather than by proper plural category, so a Slavic language gets the wrong form for most numbers with no warning at all. Worse, named date formats resolve against the short runtime locale code, so keying formats by a full regional tag returns an empty string instead of raising — every date on the page would have silently disappeared. Both failure modes are quiet; neither logs anything.
