Language: Language Binding: Language Key, Default Text, and Save Checks
This section shows how to bind a text-capable component to a language key, fill the fallback text, save the binding, and troubleshoot a translation that does not appear.
Open language binding from a text component
Select a text box, a shape that contains text, or a supported template object. In the Behavior Browser, bind Localized Text from the Text category, or open the component's Language binding editor. For an existing binding, double-click Localized Text under the component node.
- Select a component that can display text.
- A line or image without text support cannot accept a text behavior.
- Existing binding: double-click the bound behavior on the left.
- New binding: drag Localized Text from the right catalog onto the component.
Choose Enable language binding
When Enable language binding is checked, the component uses Language Key for the current runtime language. Clear it to stop using this binding while retaining the saved key and fallback text. The change is written only when you choose OK.
- Runtime language switching is required: keep it checked.
- Temporarily show fixed text: clear it.
- Choose OK after changing the state.
Fill Language Key and Default Text
Language Key is a stable, unique key from the language catalog, such as screen.pump.start. Default Text is the readable fallback shown when the key has no translation. Do not place a PLC tag, template variable, or script in Language Key.
- Reuse one stable key for the same meaning across pages.
- Match the language catalog's case exactly.
- Keep Default Text non-empty so a missing translation remains readable.
- Line breaks and surrounding spaces in Default Text are preserved.
Language Key: screen.pump.start
Default Text: Start
Verify the saved result
Choose OK, reopen the behavior, and confirm the enabled state, key, and default text. Export the page and switch between at least two available languages in HQControl. A known translation should appear; a missing translation should show Default Text.
- Reopen the editor and confirm all three values.
- Switch the runtime language and check that the component refreshes.
- Test a language without this key and confirm the fallback.
- If several components reuse a key, verify that their intended wording is the same.
Troubleshoot a missing translation in order
Confirm the binding is enabled, compare Language Key character by character, verify that the selected language contains the key, then confirm that the host changed language and refreshed page text. If the component is blank or shows a key, restore a readable Default Text first and then repair the catalog entry.
- Is Enable language binding still checked after reopening?
- Does Language Key match case and spelling?
- Does the target language contain this key?
- Is Default Text non-empty?
- Did the page refresh after the language changed?
