Skip to content

Languages (admin)

Manage the platform's translation catalogue — add or remove supported languages, track per-language coverage, and edit translation keys.

Required role

Admin. PegotecUser for cross-tenant translation work.

Not the same as the user language switcher

End users change their own language from Profile → Language. This page is for admins who manage which languages the platform supports and the underlying translation keys.

Overview

The Languages page is the admin surface for the platform's translation system. It shows every supported language, the per-language key counts across three string namespaces (Web Strings, App Strings, Component Strings), and lets you add, edit, or remove languages.

Open the page

Configuration → User Setting → Languages.

Page title: Languages & Translations.

The Languages tab

A table of supported languages with columns:

Column Meaning
Name Language name in English (e.g. "German").
Code ISO 639 locale code (e.g. de).
Translation Native-language name (e.g. "Deutsch").
Flag ISO country code used for the flag icon.
Default Whether this is the installation's default language.
Web Keys Count of translated keys in the web-portal namespace.
App Keys Count of translated keys in the mobile-app namespace.
Component Keys Count of translated keys in the component / master-data namespace.
Actions Edit / Delete buttons per language.

An Add Language button in the top-right lets you register a new language.

Example state from a production tenant:

Language Code Web Keys App Keys Component Keys
English en 0 523 221
German de 928 523 221
French fr 896 280 221
Spanish es 813 280 221
Indonesian id 754 280 221
Bengali bn 732 280 221
Chinese zh 599 280 221
Romanian ro 504 280 221
Thai th 254 280 221
Arabic ar 0 280 0
Dutch nl 0 280 0
Italian it 0 280 0
Portuguese pt 0 280 0
Turkish tr 0 280 0

(English is the reference — its web-keys count reads 0 because every string is stored as its English form; the other languages show how many translations have been loaded against the English reference.)

The other tabs

Next to Languages are three tabs for editing the actual translated strings:

  • Web Strings — UI strings used by the web portal.
  • App Strings — strings used by the mobile app.
  • Component Strings — strings tied to component definitions (labels, remarks, task names) that propagate to mobile.

Each tab opens a filterable table of keys with per-language columns so you can spot missing translations and fill them in.

Add a new language

  1. Click Add Language.
  2. Fill in:
    • Name (English) — e.g. "Vietnamese".
    • Code — ISO 639 (e.g. vi).
    • Translation — native name (e.g. "Tiếng Việt").
    • Flag — country code for the flag icon (e.g. vn).
  3. Save.

The new language appears in the list with zero translations. Use the Web Strings / App Strings / Component Strings tabs to populate.

Edit a language

Languages → (row) → Edit language.

You can change the name, native translation, flag, or default-language flag. The locale code is usually not editable after creation — it's wired into stored user preferences and changing it orphans them.

Delete a language

Languages → (row) → Delete language.

Deletion removes the language for everyone

Users who have this language set fall back to the installation default. Their preference is reset, not carried. Check with Admins before deleting.

Typically you don't delete a built-in language. You deactivate in practice by removing it from the supported-languages picker (if your installation surfaces that separately).

Edit translation keys

Switch to one of the string tabs. Each row is a translation key; each column is a language. Click a cell to edit the translation inline.

Untranslated cells fall back to English in the UI. A large number of untranslated cells in a column shows which language needs attention.

Where translations go

  • Web Strings — refreshed on every page load of the web portal.
  • App Strings — downloaded as a translation bundle on every mobile sync cycle (~15 minutes or Force Sync).
  • Component Strings — propagate via the same mobile sync.

See Language and locale for the end-user perspective.

Cross-tenant translations (PegotecUser)

If you're a PegotecUser, translations are managed centrally by Pegotec across all customers. Per-tenant overrides are possible but exceptional — most tenants consume the central catalogue unchanged.

Things to watch for

Don't rename a language code mid-flight

Locale codes are written into every user's profile. Changing en to eng breaks every user with English set. The UI typically blocks this; if it doesn't, don't.

Track coverage by column

The quickest health check: sort by one of the Keys columns descending. The bottom of the list is where translation effort is most needed.

Translation Mode (from your profile dropdown)

Some installations surface a Translation Mode toggle in the profile dropdown that shows translation keys inline on every page — useful for spotting untranslated strings while navigating the portal normally.

Troubleshooting

Problem Fix
New language doesn't appear in user profile picker It may be filtered out if it has zero translated keys; add a few and re-check
Translation edit doesn't take effect Refresh the page (web) or Force Sync (mobile)
Deleted language by mistake Re-add with the same code; translations aren't restored automatically — re-import if you have a backup
Flags missing Flag codes need to be valid ISO-3166 two-letter country codes