Page Properties |
---|
|
Product Version | 2021 Winter |
---|
Report Note |
|
---|
Assignee | Antje |
---|
Resources & Remarks Modification History Name | Date | Product Version | Action |
---|
Antje | 20 SEP 2021 | 2021 Winter | Page created. |
|
...
Section |
---|
|
Column |
---|
Table of Contents Table of Contents |
---|
exclude | (Table of Contents|Read on|Another Tutorial|Another Concept Article|Another interesting Tutorial) |
---|
|
|
|
Introduction
The terms and phrases displayed by a client application based on the framework library such as our yuuvis® client as reference implementation can be localized for custom languages according to the corresponding needs. Therefore, each individual technical term used in the background can be mapped to a user-friendly localized term or phrase that will be displayed in the browser UI wherever the technical term would be present. These configurations are defined in different JSON files. There are two global localization configuration files that are available in all tenants: one for the localization of control elements provided by the framework library (e.g., buttons or error messages) and one for the localization of terms introduced via a global schema (e.g., labels for administrative fields in object forms). Additionally, each tenant has an own localization configuration file for terms introduced via its specific tenant schema (e.g., labels for metadata fields in object forms). This article describes how to
This article is written for administrators that will prepare an application based on the reference client for a new language. There are several parts that must be configured in a specific way.
...
Info |
---|
|
Read on
Section |
---|
Column |
---|
| Another Tutorial Brief summary of the article linked.
|
Column |
---|
| Another Concept Article Brief summary of the article linked. |
Column |
---|
| Another interesting Tutorial Brief summary of the article linked. |
|
|