๐Ÿ“– This is a static documentation page. Open the interactive version with live canvas demos โ†’

Languages

The application supports 13 languages. Every label, term, and UI string is translated, with English as the fallback for any missing translation.

Supported Languages

  • DEU โ€” German
  • SPA โ€” Spanish
  • ITA โ€” Italian
  • JPN โ€” Japanese
  • POR โ€” Portuguese
  • HIN โ€” Hindi
  • KOR โ€” Korean
  • CHI โ€” Chinese
  • RUS โ€” Russian
  • MSA โ€” Malay
  • FRA โ€” French
  • TUR โ€” Turkish
  • ENG โ€” English (fallback)

Switching Languages

The language selector is located in the footer bar at the bottom of the page:

  • The ENG button is always shown
  • The current language is shown with an active highlight (if not English)
  • A "..." button opens a dropdown with all available languages
  • When English is selected, the previous language button appears for quick switching back

Your language choice is saved in a cookie and restored on next visit.


How Translations Work

All translations are stored in JSON files under the `i18n/` folder. Each file is a collection of keys, and each key maps to an object with language codes as properties:


"keyName": {
    "eng": "English text",
    "rus": "Russian text",
    "deu": "German text",
    ...
}

The getter pattern always follows the same rule: use the current language, fall back to English if missing. This means partial translations work immediately โ€” untranslated strings appear in English rather than showing blank.


Translation Files

The system uses separate files for different domains:

  • coreGroup โ€” microelement group names (reach, grasp, move, etc.)
  • coreExtension โ€” microelement subtype names
  • panelsUI โ€” panel headers and navigation labels
  • processItems โ€” process hierarchy labels (product, operation, step, action), their parameters, step types, and step groups
  • flowItems โ€” flow diagram node type names
  • uiElements โ€” general UI element labels
  • qualityFactors โ€” quality factor names for microelements
  • numericalFactors โ€” numerical factor names
  • tags โ€” tag category and value labels
  • loginPage โ€” authentication page strings
  • xmptsApp โ€” application-level strings
  • intensity โ€” work intensity labels
  • resourses โ€” resource-related strings
  • envItems โ€” environment item names
  • passport โ€” passport and BOM labels
  • cpLabels โ€” control plan labels
  • footerCopy โ€” footer copyright text
  • homePage โ€” landing page content
  • navLabels โ€” navigation labels
  • navLogo โ€” logo text

Additionally, per-language HTML files exist for the login instructions page under `locale/{code}/loginInstr.html`.


Adding a New Language

To add a new language:

  • Add a new entry to the LANGS array with a 3-letter code and label
  • Add the language code key to every JSON file in the `i18n/` folder
  • Create a `locale/{code}/loginInstr.html` file for login instructions
  • The fallback mechanism ensures partial translations work immediately โ€” any string without a translation in the new language will display in English

No application rebuild is needed for translation changes โ€” only the JSON files and the LANGS array registration.


Domain-Specific Terms

Manufacturing terminology (BES groups, step types, quality factors) is translated alongside UI strings. This means the entire domain model adapts to the user's language โ€” not just buttons and labels, but technical terms like "reachByHand" or "auxiliaryStep" appear in the local language.

The documentation system (this guide) also supports multiple languages, with matching `eng.md` and `rus.md` files for each document.