Localizing Event Triggers
Your event triggers can support the same languages that PTC RV&S supports. The following are the high-level steps to localize an event trigger:
1. Create an event trigger script file. Use tokens in the event trigger script files.
2. Create a corresponding locale-based resource bundle.
3. Add tokens to the event trigger property files in the resource bundle files.
Triggers use the following methods in the ScriptEnvironmentBean:
getMessage(String token)
getMessage(String token, Object... args)
getMessage(String token, Object... args)
For more information on the methods, see Event Trigger Java Documentation available from the PTC RV&S landing page.
Locale-based Resource Bundles
To support localization of event triggers, locale-based resource bundles can be created for supported languages.
Locale-based resource bundles consist of event trigger properties for each supported language. By default, event trigger properties are located in the following directory:
installdir/data/triggers/scripts/properties
 |
If your event triggers are not in the default directory, ensure that the event trigger properties are located in a properties subdirectory of that location.
|
The name of the event trigger properties file is derived from the event trigger script file used in the event trigger. The filename is of the form nameRB_locale.properties, where name is the event trigger script filename and locale is the locale for the language. For example, the resource bundle for the event trigger script countChild.js could consist of the following event trigger properties files:
|
Language
|
File
|
|---|---|
|
English
|
countChildRB.properties
|
|
Chinese Simplified
|
countChildRB_zh_CN.properties
|
|
German
|
countChildRB_de.properties
|
|
Japanese
|
countChildRB_ja.properties
|
|
Korean
|
countChildRB_ko.properties
|
|
French
|
countChildRB_fr.properties
|