Mapping Locale Variants to Existing Locales
When service information is authored in different variants of the languages supported by the UI, a configuration change to the data loading process can be done to map these variants to the existing locale. For example, if there is content authored in the base English locale (‘en’), an entry can be added to map the ‘en’ locale to the ‘en_US’ locale supported by the UI.
1. The following configuration file needs to be updated:
<INSERVICE_INSTALL_DIR>/Config/Applications/DataProcess/Config/Common/Templates/LanguageMappings/language-mappings.xml
2. This configuration file contains mappings from the authored language locale to the PTC Arbortext Content Delivery language locale. This mapping uses the following format:
<LanguageMappings>
<Lang src="en-us" map="en-US"/>
<Lang src="en_US" map="en-US"/>
…
</LanguageMappings>
This mapping will then be used during the load process of new data into PTC Arbortext Content Delivery.