Using Localization

Localization allows the program we wrote in the Core Framework to be used in multiple languages. For each module that you want to translate, you must create a translation file with a .json extension and a name matching the module’s name, which should be saved in the resources/Dictionaries folder within the project.

When the modules are initialized, they send the list of languages included in their assigned dictionary to the System Status Bar , which then displays them in the drop-down menu on the interface.

Once the language is selected, the translation is completed, and the translation written in the selected language is available. It is important to note that since a JSON file can be assigned to a module, if there is a label that appears in multiple places within a module, it only needs to be added to the dictionary once. Translation for the modules’ Actors occurs automatically when the language is changed, since their base class contains the Translate VI.vi that performs the translation. In other cases, such as when creating a pop-up window, this VI must be placed in the pop-up window’s Block Diagram. This VI checks all controls and displays on the front panel of the referenced VI to see if a translation is available in the dictionary.

When the language changes, the system generates a Module Event <Module Events.Language Changed>, into which we can place commands that we want to execute after the language change (example to be provided later).