Localization Workflow

The typical workflow for adding translations to a Galaxy consists of the following:

1. From the Galaxy menu, select Export, then select Localization. There are four options under Localization. If you did not select any objects in the IDE before opening the Export menu, the options for choosing selected graphics and alarm fields will not be active:

   • Selected Industrial Graphics

   • All Industrial Graphics

   • Selected Alarm Fields

   • All Alarm Fields

2. When exporting Industrial Graphics, select the language you will be adding and the destination folder. When exporting alarm fields, in addition to the language and destination folder, also select as appropriate:

   • Export all alarm messages to a single file

   • Create one translation file per area

   • Regardless of which export option you choose, there is an additional option to limit the export to only alarm messages that have not yet been translated.

     Note: For applications that only target subareas of the Galaxy, exporting by Area is a more optimal workflow.

3. Export the file and add translations for each field to be localized in the file.

4. Import the translated file(s) back into the Galaxy.

5. For InTouch HMI, import the translated language files into InTouch. No separate import is required for AVEVA OMI applications.

   • In stand-alone InTouch, you can perform a single import operation.

   • In managed InTouch, you must import the language file into each managed InTouch application.

   • For InTouch applications that only target subareas of the Galaxy, exporting by Area is a more optimal workflow.