Localize Widgets

Localize the widget to make it usable with a specific language, script, and culture. Localization for widget works the same way as it's done for AVEVA Work Tasks controls, where the key-value pairs are updated with @@ prefix and suffix.

To localize the widget

1. In the corresponding configuration file, do the following:

   • (Hierarchy Selector) In the //Title, header, and captions section, keep the default and go to step 2. That section is already set to support localization by default. You only need to ensure that the value of the properties matches the ones in the localization text file.

   • (Grid) You are given the option to localize the Grid title and the different column headers in your dataset. By default, the Grid title is already set for localization, so you can just proceed to step 2. Ensure that the value of the property matches the one in the text file.

     For the column headers, use the title field to define the text to localize under the //Columns section of the code.

     For example:

     title: WW_localize("@@WidgetBaseGridProductName@@"),

     

     This must match the item in the localization text file. For example format of the text file, see Example localization text file.

2. Open each of the widgets' corresponding wjson file and check which properties defined in the said file you want to localize. For information on wjson file, see Dynamic Widget Properties and Events.

3. Open the corresponding widget text file for localization and define the values for each of the properties. You can access the widget text files from <AVEVAWorkTasksInstallPath>\Locales\en-US\Forms2\Standard.

   • Forms_AWT<VersionNumber>_BaseGrid.txt

   • Forms_AWT<VersionNumber>_HierarchySelector.txt

4. To localize for cultures other than English (US), update the web.config file and create a separate localization text file for that language. For detailed steps on localizing for other cultures, see Developer Guide > Localization > Steps to Localize AVEVA Work Tasks.