[00:00] Through the use of localization, Ignition offers us the ability to translate texts on vision or perspective applications, to a language of your choice. A user can easily choose which language their client or session displays using a special language selector that will display the available language defined in the system. Texts contained within components that have their properties correctly mapped with localization, will be translated to reflect the user selected language. To set translations, I first have to define a new language within what we call the translation manager. I am currently in my designer. If I head to the tools menu, I will find the translation manager option. Once my translation manager opens, I will see on the left a list of all my currently available languages. In the center, you will see a table where my translation terms are defined. A translation term is composed of a key string value along with any number of translations.

[01:04] This list of terms is global and therefore shared across all your ignition projects. Before I define a translation, I have to add a new language using the plus icon on the upper left-hand corner. I will select Spanish from the language drop-down here and press okay. With my new Spanish language added, I can begin to define translation terms. I will create a new term by pressing the plus icon on the upper right-hand corner of my translation manager. I will make this new terms key value be auto, and click okay. I will now expand my new term like so and I will give it its Spanish translation and save it. I will add a new additional term and make it's key value be temperature. I will expand my new temperature term and give it a Spanish translation as well, and press save. There are other ways to add or view translation terms. In my currently open vision window, I can select say one of my labels.

[02:06] If I try and edit its text property from the property editor like this, you will see a little button on the bottom right. If you press it, you will see my auto key and it's translation listed. Say instead of auto, my label said something different. Since this new text is not defined as a translation term, if I try to see its translation you'll notice that it will be blank and I will be given the option to add it as a new term and define its translation later. From my project browser I can also right click on my windows room container and select the translations menu. This will recursively browse all the translatable properties in the components within my room container and list them out in this translatable terms panel. You'll notice in this translatable terms panel that I can have a global or a component translation. Component are specific only to that component and can only be added using the translatable terms panel.

[03:05] A global term is available both in the translation manager and the translatable terms panel. Global terms are global in that they can provide translations on all components, in all windows, and on all projects. Keep in mind that component translations will always take precedence over any globally defined translation. From the translatable terms panel, I can filter my terms, I can select or add a new language, or I can add any selected terms to my translation manager to be translated later. I'll do that. I will select all of these terms, and I will click on the add to translation manager button. Now, if I head over to the translation manager from the tools menu, you will see that all of my new terms have been added. I have defined my Spanish language and I have mapped some English words to their Spanish translations. I can now test them to see if they worked. My vision window here is displaying information for eight motors using some of the words I have translated from English to Spanish, like auto and temperature.

[04:10] To get these words to translate, I first have to grab the language selector component from my vision component palette. I will go ahead and place my designer in preview mode. And when clicking on the language selector drop-down, you will notice that it automatically knows that I have a Spanish language defined. Selecting Spanish, will cause any and all words in my application to be translated to Spanish as long as they have a translation term associated with them in the translation manager. As you can see, once you spend some time defining which terms you want translated to what language, and assign them their specific translated terms, switching between languages and ignition, it's just a few clicks away. Now in this lesson, we've explored translations envision. In a later lesson, you will learn how translations work using perspective.