IoT Cloud localization has three layers.
- Stored in code files.
- Resolved by Nette localization extension.
- URI language + default language + fallback behavior (EN fallback).
- Managed centrally.
- Include static languages and can add more locales.
- Support fallback and locale settings.
- Used for dynamic translations in DB-backed entities across DBM and instance scope (except project-language physical column model).
Resolution strategy:
- try translation for selected locale
- try locale fallback/default chain
- fallback to base column value
Project languages are project-specific and independent from global language list.
Key behavior:
- must be configured before first OT/DT generation if used
- translated columns become physical per-locale columns
- mandatory locale columns must have values; optional locale columns can be null
- used for OT/DT metadata and OT columns marked as translated
Project localization is designed for strongly structured multilingual metadata where physical schema-level translation is required.