BloomReach Experience Manager uses a mechanism called localization modules to provide the localized strings to end projects. The BloomReach Experience Manager product artifacts only contains English display strings, stored in either regular Java, repository or Angular resource bundle files. The translations for those resource bundles are made available to end-projects as separate localization modules. End-projects pull these localizations modules into their build using the “hippo-l10n-maven-plugin”, which scans the project’s dependencies and adds the necessary localization module dependencies at build time. During the build you will see log statements such as:
Include localization module 'org.onehippo.cms7:hippo-cms-l10n:jar:nl:4.0.0'.
Your project’s root pom.xml defines the property “hippo.cms.locales”, which contains a comma-separated list of locales that should be included in the build.
Note that English (EN) is provided by default and need not be listed.
The included localization module(s) for the main BloomReach Experience Manager module will automatically register its locale as available frontend locale for the BloomReach Experience Manager login page to show in the language selection dropdown.
For new BloomReach Experience Manager projects created with the BloomReach Experience Manager Maven Archetype all supported locales are by default included using the above configuration.