Languages and Localization

yuuvis® RAD designer 10.x »

The schema is part of a project. Names for schema data can be localized, that is, made available in different languages. Users select a language from the integrated language in their settings.

When you create object type groups, object types, fields, and catalogs, neutral names are initially specified. Neutral names are used if no localized descriptions exist for a language included in the schema.

Localized names are created in the Properties area or in the Localization view area.

The Localization view area contains tables for object types and catalogs with columns for each language included. These tables can be copied, pasted into external applications, edited, and then pasted back into yuuvis® RAD designer.

Integrating Languages

'German' and 'English' are integrated as default languages in a new project.

To integrate languages, follow these steps:

  1. Open the Projects area via the View ribbon tab.

    The Projects area displays a list of all open projects.

  2. Select Properties from the context menu of a project.

  3. Take the languages you want to use from the Available languages list and enter them in the Supported languages list. You can also remove them from the list.
  4. Confirm with OK.

The supported languages are displayed in the localization dialogs.

After checking and deploying the project to the server, you need to restart yuuvis® RAD core-service so the changes to the languages in yuuvis® RAD client are shown.

Localization

Individual descriptions can be localized in the Properties area. The corresponding fields are marked. Click the label to open the dialog.

The Localization view area displays a table with all localizable fields and properties for object types and catalogs. Localized names can be entered in the cells.

The table and parts of the table, such as rows and columns, can be marked and copied using standard keyboard shortcuts. In applications such as Microsoft Excel, this data can be pasted, edited, copied, and pasted back into the localization table.

The first column with the names of the properties and fields and the header line with the language names are not copied.