Ignition 8.1
Ignition 7.9
Ignition 7.8
Sepasoft - MES Modules
Cirrus Link - MQTT Modules
Inductive University
Ignition Demo Project
Knowledge Base Articles
Forum
IA Support
SDK Documentation
SDK Examples
You're currently browsing the Ignition 8.0 docs. Click here to view the latest docs.
Localization allows you to translate text into multiple languages in a project for display on client screens. The localization feature allows users located in different countries to set their default language so client screens can be displayed in their native language. The user can easily choose which language their Client displays with a click of a button! Text contained in components, that have their properties correctly mapped with localization, will change to reflect the language the user has selected. There is a special Language Selector dropdown list that displays the available translation mapping options for these translations.
All translations are stored centrally in the Gateway and are distributed to each Client and Designer. All projects share the same translations, and those translations can be used in other locations, such as Gateway scripts, and alarm messages. The full translation database can be viewed and edited in the Translation Manager tool located on the Tools menu the Designer.
You can add new terms and phrases to the Transaction Manager. Make your phrases as long or short as you like with single words or whole paragraphs. It allows users to easily import and export translatable components and share them across projects and with other users. It also has the ability to define new languages.
A central term database and support are automatically built in to all component text properties, as well as other text-based properties, such as alarm messages. Aside from defining translations for terms, there is usually no other work needed to take advantage of the translation system.
Terms are referenced in the translation database using direct string comparison. Ignition has special term Keys that are used to identify when to translate text. The base term may be a user-readable string such as "Start", or any special code you want such as "START_COMMAND" or "#start", which would have an alternate translation for English defined as "Start." This way you can quickly identify which terms will be translated when working in the Designer. To keep things simple, the English key is automatically used if no match is found for the requested language.
You can quickly and easily identify, and translate all terms by selecting a container from your Project Browser and opening the Translatable Terms panel.
If you don't see the Translatable Terms panel, go to the menubar and select View > Panels and check Translatable Terms. Here, you can see all terms for each component in the container, and if each term has an associated translation for the requested language.
You can easily preview your translations in the Designer. To change the preferred language for Preview Mode, use the Preview Language menu item under the Project menu in the Designer. When you put the Designer into Preview Mode, everything on your windows will be automatically translated. Using the Language Selector Component or scripting can temporarily change the current language, and the language will revert back any time Preview Mode is disabled. The Designer will remember your choice, even when the Designer is restarted.
In This Section ...