Configure Localized Text and verify language fallback | Mingcedar Studio

<div class="manual-doc-article manual-doc-article-section"><h2 id="language-settings">Language: Configure Localized Text and verify language fallback</h2>

Bind Localized Text to a text-capable component, set Text key and Fallback text, then verify translated and missing-key cases in the host.

<div class="doc-card-list">

<article class="doc-card">

<h3 id="language-settings-item-1">1. Open the current behavior editor</h3>

<p>Select a text-capable shape. In Behavior Browser, drag Text → Localized Text onto it; double-click an existing binding to edit it. This editor has no Enable language binding checkbox.</p>

</article>

<article class="doc-card">

<h3 id="language-settings-item-2">2. Fill the key and fallback</h3>

<p>Text key is the language-catalog key, saved as TextId. Fallback text is saved as DefaultText and appears when no translation is found. These are text fields, not Tag or JavaScript expression inputs.</p>

<ul>

<li>Match the catalog key exactly and keep a readable fallback.</li>

<li>Reuse the same key only when the intended meaning is the same.</li>

</ul>

<div class="manual-code" data-code-language="text"><div class="manual-code-toolbar"><span>Text</span><span class="manual-code-tools"><small>Text</small><button type="button" data-copy-code data-copied="Copied" data-failed="Select and copy the code" aria-label="Copy code: Text">Copy code</button><span class="manual-code-status" role="status"></span></span></div><pre tabindex="0" class="docs-code-block shiki github-light" style="background-color:#fff;color:#24292e" tabindex="0"><code><span class="line"><span>Text key: screen.pump.start</span></span>

<span class="line"><span>Fallback text: Start</span></span></code></pre></div>

</article>

<article class="doc-card">

<h3 id="language-settings-item-3">3. Save and reopen</h3>

<p>Choose Save, reopen the behavior, and verify both fields. Cancel discards the current edit; canceling a newly added behavior rolls back that new binding. To remove localization, remove the behavior and set the intended fixed text.</p>

</article>

<article class="doc-card">

<h3 id="language-settings-item-4">4. Verify three runtime cases</h3>

<p>Export and load in Mingcedar. Check a language that contains the key, a language with no matching translation, and an empty fallback. The order is translation → Fallback text → key.</p>

<p class="doc-step-result"><strong>Expected result</strong> The component updates after switching the host language and remains understandable when a translation is missing.</p>

</article>

<article class="doc-card">

<h3 id="language-settings-item-5">5. Troubleshoot in order</h3>

<p>Check the binding, exact key, target-language catalog and active host language. Text lookup is distinct from a PLC value read; changing a Tag does not repair a missing translation.</p>

<ul class="doc-related-links">

<li><a href="/en/ppt/manual/localized-text-behavior/">Localized Text behavior reference</a></li>

</ul>

</article>

</div>

</div>