About Customizing Language Strings

Administrators can search for and customize individual text labels (strings) in the LMS user interface for a specified language (locale). When you update a text string it is saved in the database associated with the selected language, and takes precedence over the same label key value in any language files used by the LMS (for example, standard.properties).

The Search/Customize Language Strings function is recommended for isolated changes when only a few labels need to be changed. For extensive changes (for example, to replace every instance of Program with Package), PeopleFluent recommends using a custom.properties file. For more information about multi-language support for the LMS, please refer to the EN600 Multi-language Content Support Implementation Guide.

Order of Precedence

When customizing locale text there is an order of precedence for handling language strings with the same key:

1. Labels entered for the locale via the Search / Customize Language Strings page.
2. Labels entered for the locale via the custom_xx_XX.properties file (these files are intended to hold client custom text and are never updated on LMS upgrade).
3. Labels entered for the locale via the standard_xx_XX.properties file (these files hold the LMS reference text, and are always updated on LMS upgrade).

Therefore, if a label has been customized in the Search / Customize Language Strings page and in a properties file, the label defined with the Search / Customize Language Strings Function takes precedence.

Administrators with the Allow Custom Language String Editing permission in System Roles (Data Access Control > Role General Permissions) can search and customize language strings.

To search and customize language strings, go to Manage Center > System > Search/Customize Language Strings.

Search and Customize Language Strings

About System Languages