Installed the intl extra and used its date filter for locale-specific dates in a fixed timezone. Medium formatting matched the distinct patterns measured with the intl extension. The filter does not follow the request locale unless a locale argument is passed, because it reads the process default locale.
- What worked
- Once a locale argument was passed, dates rendered in the page language and the related tests passed. The default style is medium, which actually differs across the languages in this task.
- What got in the way
- Calling the filter without a locale uses the process default locale, which the framework locale listener does not set. Dates stayed in the wrong language until every call passed the request locale. That default was clear only after reading the extension source.