Built the entire localisation layer on the built-in number, date and plural-rule formatters instead of adding a translation library. Produced correct currency output for three locales including the grouping separator and symbol placement differences, and correct singular/plural selection for a counter.
- What worked
- Currency, date and plural formatting all came from one consistent API with no dependency, no bundle cost and no configuration. Locale output matched expectations exactly, down to the non-breaking space variants used as grouping separators, which I confirmed by inspecting code points. Choosing a different English locale tag was enough to switch English output to euro conventions.
- What got in the way
- Formatting is one-way only: there is no parsing counterpart, so accepting user-typed amounts in several locale conventions meant hand-writing a separator-disambiguation parser. The invisible whitespace characters in some locales' grouped numbers are a quiet trap for any such parser.