...
| Page Properties | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
Resources & Remarks Modification History
@Antje : Peter hat mir zwei links gegeben, über die man in einem installierten System sowohl an die Custom Client Keys als auch die Framework Keys kommt: Der Cliet läuft in 'litedms' ... Wenn Du eine gute Idee hast, das als alternativen Zugang zu den Client-Keys unten einzubauen ... |
...
The terms and phrases displayed by a client application based on our libraries such as our yuuvis® client as reference implementation can be localized for translated into custom languages according to the corresponding needs. For this purpose, 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 client application wherever instead of the technical term would be present. The built with our libraries allows for the localization of control elements (e.g., buttons or error messages). In order to provide a custom language in the selection list from which the users can select their preferred language, it has to be added to the client's main configuration. Furthermore, labels used in forms can be localized easily during runtime.
...
The localization of control elements is realized directly during the building build process of the client. JSON files are used as configuration files for the translations. The languages to be offered to users are specified in the client's main configuration.
>> Framework Library Installation and Configuration
...
The labels displayed in forms (e.g., object metadata forms) are localized by means of JSON configuration files as well. A distinction is made between tenant-specific labels available only within in one tenant and global labels available in all tenants. The tenant-specific localization files are managed by users with the role the YUUVIS_TENANT_ADMIN role. Their changes are applied only to their own tenant. Users with the role YUUVIS_SYSTEM_INTEGRATOR role are allowed to manage the global localization files available in all tenants.
Whenever a new tenant is created and provided with its own tenant-specific resources like, e.g., a tenant schema, also a tenant-specific localization file also needs to be created. Otherwise the technical terms defined in the technical resource files will be displayed in the forms.
...
| User Role | Available Endpoints for Localization Management | Description | ISO Language Specification | Range of Application of managed Localization Files | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| YUUVIS_TENANT_ADMIN | GET /api-web/api/admin/resources/text |
| in the request header Accept-Language | Tenant-specific: available only within in the tenant the currently logged-in user belongs to. | ||||||||
| POST /api-web/api/admin/resources/text/{locale} |
| as path parameter | ||||||||||
| YUUVIS_SYSTEM_INTEGRATOR | GET /api-web/api/system/resources/text |
| in the request header Accept-Language | Global: available for all tenants. | ||||||||
| POST /api-web/api/system/resources/text/{locale} |
| as path parameter |
...
In case you need to extend translations with new keys, please specify translations within in the plug-in configuration for each language in your system.
>> Extending the Clients with Plug-ins
...