Management of a default language per instance
Allow community platforms to have a default language chosen by the client (Each client must be able to choose its default language for its platform, this will certainly require a deployment setting).
It is necessary to activate the fallback to the default language on the components that do not have it yet ( In particular Event).
For the fallback, JB told me about the i18n component.
The process will be as follows: The platform will take into account the language defined on the client's browser to display the pages (as it is already done today), If the language files are present for this language and for the component to display, the component will use these translation files to display the pages. If the language files are not present for this language for the component to display, the component will use the translation files of the default language to display the pages.
Obviously, it is up to the POs to ensure that the default language requested by the customer exists on the components to be deployed, otherwise the customer can contribute to provide us with the translation files in the desired language.