Localized Text

What it is and what it's for

Bind Localized Text to a text component to look up its key in the global translation table. Host language changes update the display automatically, without separate pages per language.

Field configuration

In Behavior Browser, add Localized Text to a text-capable component and enter Text key and Fallback text. This mode has no script or quality override settings.

• Text key (Text ID): enter the language-catalog key, for example pump.start.
• Fallback text (Default Text): readable text used when no translation is found.
• Fallback order: 1) translation from the current language pack, 2) Default Text, 3) the key itself (meaning no translation matched).
• Export note: the editor warns that text is flattened to one line, so multi-line content is collapsed.

Text key: pump.start
Fallback text: Start pump

When to use it

Use it for multilingual screen text, for example:

• A Start button bound to one Text Key (e.g. pump.start): shows 'Start' in English, '启动' in Chinese, from the same shape.
• Screen titles, device-status text, and navigation menu items all driven by language keys, so switching the runtime language updates them all at once.

Limitations and troubleshooting

The host controls the active language; use hqVisuDesigner.useLanguage(...) to switch it from script. Missing translations display the configured fallback, then the key.