Configuration files used for globalization

You use Guidewire Studio™ to edit the configuration files for globalization. The following list describes the configuration files and how to navigate to them in the Project window.

configuration > config
config.xml
  • Configuration parameters related to localization. The localization-related configuration parameters include, among others:
  • DefaultApplicationLocale
  • DefaultApplicationLanguage
  • DefaultCountryCode
  • DefaultPhoneCountryCode
  • Each Guidewire application instance contains a single copy of config.xml.
configuration > config > Extensions > Typelist
Country.ttx, Country.default.ttx
  • Country codes that reflect the Unicode Common Locale Data Repository (CLDR) country names.
Currency.example.ttx
  • Contains examples of currency code and similar information for the supported currencies.
Jurisdiction.ttx, Jurisdiction.example.ttx
  • Used by a number of PCF files to display a list of states or provinces, as well as jurisdictions that are not states or provinces.
LanguageType.ttx
  • List of languages that you want to have enabled in PolicyCenter.
Important: During development, if you make a change that requires that a language typecode in this typelist not be in effect when you restart, you must retire the language typecode. Do not delete the language typecode, or you might have database errors when you restart the application.
PhoneCountryCode.ttx
  • Phone country codes.
State.ttx
  • Address configuration.
StateAbbreviation.ttx, StateAbbreviation.example.ttx
  • Defines abbreviations of the names of states,provinces, territories, and so on by country.
configuration > config > Localizations
collations.xml
  • Collation configuration for one or more languages that apply to one or more database types.
localization_localeCode.xml
  • (Example: localization_en_US.xml) Currency formatting information for use with single currency rendering mode only. Defines other region settings like date and time formats and numeric separators. Studio supports multiple localization files.
language_languageCode.xml
  • (Example: language_de_DE.xml) Contains collation definitions, input field label width, and date-time field hints for a specific language.
configuration > config > Localizations > Resource Bundle 'display'
display_languageCode.properties
  • Application display keys for a specific language. Each region must have a separate display_languageCode.properties file. A display_languageCode.properties file defines standard Java properties by using the following format:
  • display_key_name = value
display.properties
  • Application display keys for the fallback language. In the base configuration, this file contains display keys for U.S. English.
configuration > config > Localizations > Resource Bundle 'typelist'
typelist_languageCode.properties
  • (Example: typelist_de.properties) Application typecode names and descriptions for a specific language.
typelist.properties
  • Fallback language for typelist properties. In the base configuration, this file contains U.S. English typelist properties.
configuration > config > Localizations > Resource Bundle 'gosu.display'
gosu.display_languageCode.properties
  • (Example: gosu.display_de.properties) Contains Gosu error messages. Studio displays these messages if it encounters a Gosu error condition. You can translate these error messages into the languages of your choice.
gosu.display.properties
  • Fallback language for Gosu properties. In the base configuration, this file contains U.S. English values for Gosu properties.
configuration > config > Localizations > Resource Bundle 'productmodel.display'
productmodel.display_languageCode.properties
  • (Example: productmodel.display_de.properties) Display keys for the fields used in the PolicyCenter product model. Except for U.S. English, the text strings in this file are in the language specified by localeCode.
productmodel.display.properties
  • Fallback language for product model display properties. In the base configuration, this file contains U.S. English values for product model display keys.
configuration > config > Metadata > Typelist
LocaleType.tti
  • List of defined regions.LocaleType.tti
PhoneCountryCode.tti
  • List of country code values for phones.
configuration > config > currencies currencyCodeFolder
currency.xml
  • Regional format overrides for monetary amounts in installations with multiple currencies.
configuration > config > datatypes
*.dti
  • Data-type declarations for column types in the data model.
configuration > config > fieldvalidators
datatypes.xml
  • Default values for precision and scale values in the default currency.
fieldvalidators.xml
  • Format information for fields such as currencies, phone numbers, and ID fields, and other fields that need validation and input masks. Does not apply to date-time fields.
configuration > config > fieldvalidators countryCodeFolder
fieldvalidators.xml
  • Field validation definition overrides by country.
configuration > config > geodata
countryCode-locations.txt
  • Mapping between postal codes and cities for a country.
configuration > config > geodata countryCodeFolder
address-config.xml
  • Address configuration by country.
country.xml
  • Visible address fields and display keys for the state and postal code labels.
zone-config.xml
  • Zone information for a specific region. Zones are address components used for address autofill and region creation.
configuration > config > phone
nanpa.properties
  • Area codes as defined by the North American Numbering Plan Administration (NANPA). These area codes apply to North American countries other than the United States.
PhoneNumberMetaData.xml
  • Area codes and validation rules for international phone numbers. See the comments at the beginning of the file for more information.
PhoneNumberAlternateFormats.xml
  • Additional area codes and validation rules for international phone numbers. See the comments at the beginning of the file for more information.