New and changed in globalization in 10.0.0
New process for enabling languages
All language translations that Guidewire supports are provided directly in Guidewire Studio localization files at the time PolicyCenter becomes generally available. To enable a language, such as a display language, you use Studio to indicate that a language is to be used in the product, and then restart the application server.
See also
Language packs no longer used to install languages
PolicyCenter 10.0 ships with all files needed for the languages supported by Guidewire. You no longer need to install a language pack to enable languages in addition in U.S. English.
See also
Changes in effects of setting the DefaultApplicationLanguage
The primary display language defined in DefaultApplicationLanguage does not cause that language to become a fallback for any other language. Setting the primary display language does set the default preferred language for new users. A user always has a preferred language, and the default preferred language is the primary display language defined in DefaultApplicationLanguage.
A user can set their preferred language to any language that you have enabled for PolicyCenter.
See also
PolicyCenter uses language fallback
PolicyCenter uses strict language fallback to resolve missing display and typecode keys for the user's preferred language. In the base configuration, U.S English is defined as the primary display language and is the base language for language fallback.
See also
Localizations folder in Studio has new subnodes
In PolicyCenter 9.0, the Localizations folder in Guidewire Studio displayed files directly in the folder.
In PolicyCenter 10.0, there are nodes under Localizations that group files as follows:
- Resource Bundle 'display'
- Contains display key files for all the language translations provided in the base configuration.
- Resource Bundle 'gosu.display'
- Contains Gosu display key files.
- Resource bundle ‘typelist’
- Contains property files for all the typecode language translations provided in the base configuration.
- Resource bundle ‘productmodel.display’
- Contains display key files for all the product model language translations provided in the base configuration.
See also
Base fallback display key properties file renamed display.properties
In the base configuration of PolicyCenter 9.0, the
en_US display properties file was named
display_en_US.properties. In the base configuration of PolicyCenter 10.0, this file is now named
display.properties and is the base display properties file for language
fallback.
See also
Base fallback typelist language properties file renamed typelist.properties
In the base configuration of PolicyCenter 9.0, the
en_US typelist properties file was named
typelist_en_US.properties.
In the base configuration of PolicyCenter 10.0, the
en_US typelist properties file is now named
typelist.properties and is the base typelist properties file for
language fallback.
See also
Base fallback Gosu display properties file renamed gosu.display.properties
In the base configuration of PolicyCenter 9.0, the
en_US Gosu properties file was named
gosu.display_en_US.properties.
In the base configuration of PolicyCenter 10.0, this file is now named gosu.display.properties.
See also
Base fallback product model display properties file renamed productmodel.display.properties
In the base configuration of PolicyCenter 9.0, the
en_US product model properties file was named
productmodel.display_en_US.properties.
In the base configuration of PolicyCenter 10.0, this file is now named productmodel.display.properties and is the base product model display properties file for language fallback.
See also