Templates or component bindings or separate client

Ignition
, ,
1

Hello Ignition world,

I have a vision client running on 7.9.21. I'll need to convert the client to Spanish now as it'll be used by a different audience. I thought of three ways to accomplish this (maybe there is more?):

  1. Put a expression binding directly on all the text components, buttons on every window / template to switch between english and Spanish based on a common tag.
  2. Create duplicate templates and windows in Spanish (just like the english ones) and use scripting to display the appropriate one
  3. Build a whole separate project under the gateway with everything on the client in Spanish.

Which option would be most efficient from a performance perspective, we don't want to overload the computer that's running the gateway and the client. (typically only 1-2 vision clients will be running per Gateway). Open to other ideas as well. Thanks in advance!

2

What about using the translation manager?
Tools > Translation Manager

2 Likes
3

Thanks a lot for the quick help! I didn't know about this. Seems like I have multiple options to add key term translations manually. But if I add some translations from the translation manager at the global level, I don't see some words getting translated. Can this manager look at every component's custom properties, template properties or internal properties?

4

It is a mix. Properties that are generally static for display purposes are translated for you (mostly), while properties that are driven by live data are not (mostly). It varies from component to component. (Perspective is more comprehensive than Vision, last I checked.)

1 Like
5

Sounds good! Thanks for the explanation, Phil