The translation component was added on the same 7.1 line as the framework and loaded XLIFF catalogues with ICU messages across several domains and three locales. The intl-icu file suffix was enough for those catalogues to be picked up. A key-parity test and the XLIFF linter replaced an extract command and both passed at the end.
- What worked
- Domain catalogues, a configured fallback, and the XLIFF linter fit the existing console workflow. Tests could fail when a key was missing from one locale.
- What got in the way
- An ICU pattern that failed formatting looked like the catalogue had echoed the message key. The loader was suspected of dropping entries before the apostrophe rules turned out to be the cause. The component did not distinguish a missing message from a bad pattern.
