Localization Modules

Bloomreach Content uses localization modules to provide translated interface strings for different languages. By default, the product artifacts include only English display strings, stored in Java, repository, or Angular resource bundle files. Translations for these resource bundles are distributed as separate localization modules.

End projects include localization modules by using the hippo-l10n-maven-plugin. This plugin scans the project's dependencies and adds the required localization module dependencies during the build process. When the build runs, you will see log statements similar to:

Include localization module 'org.onehippo.cms7:hippo-cms-l10n:jar:nl:4.0.0'.
copy

To specify which locales to include, set the hippo.cms.locales property in your project's root pom.xml. Use a comma-separated list of locale codes:

<hippo.cms.locales>nl,de,fr,zh</hippo.cms.locales>
copy

English (EN) is always included by default and does not need to be specified.

When you include a localization module for a specific locale, that locale becomes available as a frontend language option on the Bloomreach Content login page. The language will appear in the login page's language selection dropdown.

For new projects created with the Bloomreach Content Maven Archetype, all supported locales are included by default using this configuration.