Localization

Tungsten ships complete system-message catalogs. Set language on a form or editor; you do not need to translate Tungsten’s own controls, validation messages or editor text. Only the selected catalog and configured fallback are loaded. English is the default.

<Tungsten schema={schema} language="de" onSubmit={onSubmit} />

Supported package languages

• en — English
• sk — Slovenčina
• hu — Magyar
• de — Deutsch
• es — Español
• fr — Français

Regional tags such as de-DE, es-MX and fr-CA use the corresponding base-language messages while keeping regional formatting. Custom catalogs are selected by their exact configured language key. The website’s languages are independent of this package list. RTL layout remains a future feature; no RTL languages are advertised as supported.

Download the complete English JSON

Custom labels and overrides

A German-only form can use literal labels such as Vorname without any JSON. For translated labels or message overrides, use one flat JSON dictionary. Include only the keys you need; copying the system catalog is optional.

{
  "contact.name": "Vorname",
  "tg_ui_submit": "Antrag abschicken"
}

import de from './locales/de.json'
import { Tungsten } from '@myoon/tungsten/react'
const config = { i18n: { translations: { de } } }
<Tungsten schema={schema} config={config} language="de" onSubmit={onSubmit} />

Resolution order: selected custom catalog, selected bundled catalog, configured fallback-language custom catalog, configured fallback-language bundled catalog, bundled English, then the original string or key. An empty string intentionally displays empty text. Null is not a valid translation entry.

Add a language or start from the template

For a language not listed above, download the blank template and fill its entries, or copy selected system keys into your existing language JSON. Configure that catalog under your language tag. Missing keys use the fallback chain. You can also import official JSON catalogs through @myoon/tungsten/locales/<language>.json.

Download the blank system-message template

The template contains every system key with an empty string. It is a template, not a ready-to-use translation: loading it unchanged intentionally makes all system messages empty. Delete unused entries to keep their defaults; preserve parameters such as {min} and {count} when writing translations.

import cs from './locales/cs.json'
const config = { i18n: { translations: { cs }, fallbackLanguage: 'en' } }
<Tungsten schema={schema} config={config} language="cs" onSubmit={onSubmit} />

Schema text

{
  "type": "text",
  "key": "name",
  "view": {
    "label": "contact.name",
    "placeholder": "contact.placeholder"
  },
  "validators": [
    {
      "kind": "min_length",
      "value": 5
    }
  ]
}

{
  "contact.name": "Name",
  "contact.placeholder": "Enter your name",
  "tg_validation_min_length": "Must contain at least {min} characters."
}

Labels, descriptions, placeholders, option labels, group triggers, repeater labels, validation and library controls use the same resolver. Field keys, IDs and entered/submitted values retain their meaning.

Loading and switching

{
  "i18n": {
    "directory": "/locales",
    "fallbackLanguage": "en"
  }
}

A directory is a browser-accessible URL serving language.json files. Individual translations entries can also be file URLs. Requests use the API executor with operation i18n and no inherited application credentials. The previous catalog stays visible while its replacement loads; missing or failed files fall back safely. Changing language does not reset values, rerun rules, reload schemas, fetch data sources or emit a save/state event.

Custom renderers

<TungstenLang>{field.view.label}</TungstenLang>
const { t, language, loading, error, reload } = useTungstenLang()
<input placeholder={t(field.view.placeholder)} />

Use TungstenLang for visible text and the hook for string attributes. TungstenLanguageProvider can wrap an entire editor or several components. reload rereads its configured catalogs in JavaScript. Provider status exposes translation loading/failure for host-owned indicators.

Messages and plural forms

{
  "messageKey": "tg_validation_min_length",
  "params": {
    "min": 5
  }
}

{
  "tg_ui_errors": {
    "one": "{count} error",
    "other": "{count} errors"
  }
}

Core validation messages carry keys and parameters. Authored rule errors use lookup with literal fallback. Parameters are literal unless passed as nested messages. No HTML or code evaluation is used. Date/time entry follows the selected locale with expected-format feedback. Custom masks and RTL layout are outside the 1.0 API.

Existing system keys

The reference lists every shipped key, what it controls, its English default and required parameters. A system key can be overridden in the same JSON as your custom labels. Reference descriptions remain in English.