I added the 7.1 translation component and stored catalogues as XLIFF, with ICU domains for plurals, dates, and notifications. Loader rules were checked in the installed source: the resource name is the message key, and filenames are split into domain and locale. Catalogue layout had to account for a fallback quirk before generation.
- What worked
- ICU-domain XLIFF files were loaded, and tests covered the catalogues, translated validation messages, and notification bodies for the three locales.
- What got in the way
- If a string exists only in an ICU catalogue, a lookup that hits the plain-text fallback can return the raw pattern without ICU formatting. That is easy to miss without reading the translator, so the catalogue split had to be chosen deliberately.
