Localised Labels
How to give a chart or server a label per language, and the exact order Infohub falls back through when a viewer's culture has no translation.
A site with operators in more than one language does not want two copies of every dashboard. Infohub can hold several translations of the same label and show each viewer the one matching their culture.
The feature is deliberately narrow. It translates specific display text, not the model: object names, measure names and data stay as they are.
What can be localised#
| Object | Property |
|---|---|
| Chart | Label |
| Server | Label and Description |
In Flow Config these fields carry a small culture button beside them. Opening it gives you a list of cultures and the text to show for each. The object's ordinary Name remains the untranslated identifier — it seeds the default entry and is what you keep referring to in the model, the CLI and support conversations.
How Infohub picks which one to show#
When a viewer's culture is, say, en-GB, Infohub resolves the label in this order and stops at the first hit:
- Exact culture match — an entry stored for
en-GB. - Same language, any region — the first entry whose language matches, so a viewer on
en-GBsees theen-UStext if that is the only English there is. This is what makes the feature practical: you store one entry per language and every region of it works. - The
defaultentry — the fallback for every culture you did not translate. - Nothing — an empty string.
Always fill in the default. Step 4 is the trap. If there is no default entry and the viewer's culture does not match anything, the label resolves to an empty string — not to the object's name. The chart renders with a blank title rather than an obviously wrong one, which is considerably harder to notice and to report.
Region matching is on the language prefix only, so pt-BR will satisfy a viewer asking for pt-PT. Where the wording genuinely differs between regions, store both explicitly rather than relying on the fallback.
A workable approach#
- Fill the default first, before adding any translation. It is the safety net for every culture you have not thought about.
- Translate by language, not by region. One
frentry servesfr-FR,fr-CAandfr-BE. Add a region-specific entry only where the wording must differ. - Keep names untranslated. Localise the label; leave the name as the stable identifier everyone can search for.
- Check with the viewer's culture, not yours. A label looks fine to the person who wrote it by definition. Sign in as a user set to the target culture, or change the browser's language, before calling it done.
Number and date formatting is a separate mechanism — see Format Strings.
Diagnosing#
| Symptom | Likely cause |
|---|---|
| A chart title is blank for some users | No default entry, and their culture matched nothing |
| Everyone sees the same language | Only a default entry exists, or every viewer resolves to the same culture |
| A viewer sees the wrong region's wording | Language-prefix fallback matched another region; add an explicit entry for theirs |
| The translation did not appear after editing | The chart was not redeployed — see Deploying Configuration |
| Names still appear untranslated | By design; only the labels listed above are localised |