Localizing display keys

PolicyCenter initializes the display key system as it scans for the display key property files. These files are named display.properties for the fallback language (U.S. English in the base configuration) and display_languageCode.properties for additional languages. For example, display keys in German are in the file display_de.properties.

You can see these files in Guidewire Studio™ by navigating to configuration > config > Localizations > Resource Bundle 'display'.

This node contains display key property files for each of the languages supported by Guidewire.

It is possible to provide translated display keys in either of the following ways:

Translation technique	Related topic
Using the Studio Display Keys editor	Localize display keys by using the Display Key editor
Using the display key import and export tools	Exporting and importing string resources

Many of the display keys you localize are string values that PolicyCenter displays as labels or messages. There are no restrictions on the translated text for these types of display keys.

You can also localize QuickJump commands in display key property files. When you localize a QuickJump command, there must not be any spaces in the translated text. For example, the following base configuration display key in display.properties must be translated into a term with no spaces:

Web.QuickJump.RunBatchProcess = RunBatchProcess