This feature lets you specify which texts in your HMI should later be translateable. Every text you define in your HMI will be automatically saved in the translations tables of your HELIO instance. You can view all of your translations using the Translation Manager .
After you’ve created an HMI with lots of Translatable Texts your Translation Manager will look something like this 👉.
Each new translation you’ve created in your HMI will lead to a new entry in this table.
The text you enter for this property will be used as the Translation Key. This key uniquely identifies a translation throughout your HELIO runtime and across all the projects.
In this example, "Temperature" is the Translation Key. Whenever you enter this text in another part of the HMI, it will be automatically translated to "Temperatur" if the language is set to German aka de-DE.
Using the Default Language
This is the default approach. You simply enter text for your elements in the Content Editor using the your default language.
This is very intuitive and fast way to get started with becoming translabtable.
Using Unique Identifiers
Another approach that is often taken when building more complex and larger amounts of different HMIs is to start thinking about how to organize your translations more effectively.
Provide a unique identifier that clearly conveys the purpose of a translation. Organize this identifier into distinct categories or namespaces.
You can use {variable} syntax to create placeholders in your text.
In this example, the value of the variable temperatureLevel will be inserted into the label.