About localization workflow

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

1. From the Galaxy menu, select Export, select Localization., then choose which option you want to use. If you did not select any objects in the IDE before opening the Export menu, the options for choosing selected graphics, alarm fields, and internationalized strings will not be active:

   • All internationalized strings

   • Internationalized strings from selected objects (inactive if no objects were selected)

   • Selected Industrial Graphics (inactive if no objects were selected)

   • All Industrial Graphics

   • Selected Alarm Fields (inactive if no objects were selected)

   • All Alarm Fields

2. When exporting Industrial Graphics or internationalized strings, select the language you are exporting for translation and a destination folder.

   When exporting alarm fields, select as appropriate:

   • Export all alarm messages to a single file

   • Create one translation file per area

   • You can also limit the export to only alarm messages that have not yet been translated.

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

   When exporting internationalized strings, you can also limit the export to strings that have not yet been translated.

3. After exporting the file, 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.

   • 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.

   Since AVEVA OMI applications access the imported files directly from Application Server, there is no additional import required for AVEVA OMI applications.