Authored roughly eighty message keys across three catalogues against this library's message format, wrote a custom plural resolver for a language with more than two plural forms, and used its translation component with a named slot to keep inline markup inside a translated sentence. All of it rendered correctly in both server and client contexts.
- What worked
- Plural resolution is pluggable per language, which is what made a non-English-style plural system possible at all. Named placeholder interpolation and the component-with-slots form for sentences containing markup both behaved predictably. The message catalogue format is plain JSON, which made it trivial to merge runtime overrides on top of bundled defaults.
- What got in the way
- The pipe character is a plural separator in the message syntax, so two ordinary source strings containing a literal pipe would have silently become bogus plural forms. Nothing warns about this; I only caught it by reading the catalogue carefully. A lint or load-time warning for suspicious separator counts would have saved a real production bug.
