In this page we will describe how to enable and configure the multilingual support.
The platform allows a full internationalization of the UIs for both the frontend than the backend. To enable the support for multiple language the following properties must be defined in the dspace configuration
# Default Locale # A Locale in the form country or country_language or country_language_variant # if no default locale is defined the server default locale will be used. default.locale = en # All the Locales, that are supported by this instance of DSpace # A comma-separated list of Locales. All types of Locales country, country_language, country_language_variant # Note that the appropriate file are present, especially that all the Messages_x.properties are there # may be used, e. g: webui.supported.locales = en, es
The backend uses the JAVA messages properties file to translate text used in the REST API or dynamically resolved in other template. Such files MUST be available as resource in the JAVA classpatch of the webapp or the command line scripts. The English file can be used as default to make further translation, community managed translations are available in the dspace-api-lang github project.
The submission forms are configured via the submission-forms.xml configuration file that can be replicated with language postfix (i.e. submission-forms_es.xml) to provide input screens specific for each language. Similarly, the notification messages can be translated providing template in the different language.
The angular frontend uses JSON files to resolve keys in actual labels for the users. The English file can be used as default to make further translation, community managed translations are available in the same folder. The file must be named using the ISO 639-1 code of the language and the extension .json5 (i.e es.json5)
