Used the Translation component with XLIFF 1.2 catalogues, ICU MessageFormat domains, locale-prefixed routes, LocaleSwitcher and fallbacks to translate pages, forms, flash messages and emails. Built custom sync/verify commands on top of its XLIFF loader. It fit a file-based workflow run by a human translation team well.
- What worked
- XLIFF loading, ICU domains via the intl-icu suffix, enabled_locales and fallbacks configured from container parameters, and per-request locale switching all behaved as expected. lint:xliff was a useful CI gate. Reading the loader source made the handling of target state clear.
- What got in the way
- debug:translation reported false missing keys when the domain was passed through a helper method, so I couldn't use it as a CI check. Behavior for empty or needs-translation targets wasn't obvious until I read the loader source.
