Locales and language resources | Mingcedar

<div class="manual-doc-article manual-doc-article-section"><h2 id="localization">User guide: Locales and language resources</h2>

Enable the required locales, then maintain translations and import or export language resources.

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

<article class="doc-card">

<h3 id="localization-item-1">Locale Settings</h3>

<p>Location: Admin → Locale Settings. Requires language:manage.</p>

<ol>

<li>Create or edit a locale with its code, name and enabled state. The code identifies its column in language resources.</li>

<li>Choose the default locale and save. Check the runtime language selector and individual user language settings.</li>

</ol>

</article>

<article class="doc-card">

<h3 id="localization-item-2">Language Bundle: create, edit and filter</h3>

<p>Location: Admin → Language Bundle.</p>

<ol>

<li>Filter by module, search locale and keyword. Coverage and missing markers identify incomplete translations.</li>

<li>Create an entry, choose a module and enter its Key, then fill the enabled locale fields and save.</li>

<li>Open an existing entry to edit translations. Built-in entries can be edited but not deleted; user entries can be deleted.</li>

<li>Built-in entries are hidden by default. Enable Show Built-in Language Entries under Settings → Display &amp; operation to reveal them. This preference applies immediately.</li>

</ol>

</article>

<article class="doc-card">

<h3 id="localization-item-3">Import and export language bundles</h3>

<p>Import supports CSV, JSON and NDJSON; export supports CSV and NDJSON.</p>

<ol>

<li>Export an existing bundle as a format template. Keep the Namespace, Key and locale columns in CSV, and enter translations in the matching locale columns.</li>

<li>Import the file and review created, updated, skipped and failed counts. Correct failed rows according to the reported result.</li>

<li>Choose All visible entries or Current filter, select the export format and download.</li>

<li>Hidden built-in entries are excluded. To include them, change the visibility preference first and check the export scope.</li>

</ol>

</article>

</div>

<div class="docs-note-grid manual-doc-image-grid">

<figure class="docs-note-card manual-doc-image-card" id="localization-image-1" data-after-card-anchor="localization-item-1">

<img src="/WEB_img/HQserver/current-20261023/locale-settings.jpg" alt="Mingcedar Locale Settings page" loading="lazy" decoding="async" />

<figcaption>

<strong>Figure 1: Locale Settings</strong>

<p>The locale list shows codes, names, enabled and default status, with a form below for adding a locale.</p>

</figcaption>

</figure>

<figure class="docs-note-card manual-doc-image-card" id="localization-image-2" data-after-card-anchor="localization-item-2">

<img src="/WEB_img/HQserver/current-20261025/language-bundle.jpg" alt="Mingcedar Language Bundle new-entry drawer" loading="lazy" decoding="async" />

<figcaption>

<strong>Figure 2: Language Bundle: new entry</strong>

<p>The new-entry drawer has Module, Key, and translation fields for enabled locales.</p>

</figcaption>

</figure>

</div>

</div>