Status: Unverified
GOAL:
What is the Entity Translation
GOAL:
How to use Entity Translations
GOAL:
Dynamics 2.1A SP03
FACT(s) (Environment):
Dynamics 2.1A
FIX:
Dynamics allows for the translation of field meta-information, such as labels, as they appear in visual objects, for example on browser columns and viewer widgets. This widget-based translations can be defined for a specific window or globally.
There are places that require field labels to be translated where widget-based translations do not apply. In particular, the Find/Filter dialog uses field labels as row data in it's interface.
The Entity Translation allows translation of fields at the Entity object level, such that places where field information is obtain via the datafields of an entity, the translated label and column label of the fields are used. Entity-based translations are available to DynBrow and DynView objects linked to a DynSDO, and to DynView objects linked to a static SDO.
To use Entity Translations, create datafield translation records for the desired fields in an entity that is already defined in the Dynamics Repository.
The datafield translation records can be created using any of the following methods:
Translation Maintenance window (manual creation)
By migrating widget-based translations using the Migrate Widget Translation tool
By using the Datafield Translation window (available in the corresponding OpenEdge 10 release)
Since widget-based translations are applied at runtime after visual objects are created, widget-based translations are used even if an entity-based translation is available for a given field.
Note: Automatic resizing and positioning of widgets with translated labels do not occur when using entity-based translations, therefore, widgets in windows need to be given enough space to display the translated labels without overlaping the fields.
Manual creation of Entity-based Translations
The standard Translation Maintenance window (Administration window, Application->Translation Control->Translation Maintenance), can be used to create entity-based translation records, by creating a translation record for the desired language, entity and datafield name. A value of 1 for the widget entry field specifies a label, and a value of 2 a column label.
Example:
The following example shows an entity-based translation for the column label of the field State.Name:
Language: Example Language
Source Language: EN-US
Object name: State
Widget type: DataField Widget entry: 2
Widget name: StateName
Original label: State Name
Translation label: Example Translation
The fields Original tooltip and Translation tooltip are not used and should be left blank.
Generate Client Cache
The Generate Client Cache window now includes a combo-box labeled Language to select the language for the generation of the persistent cache files. The combo-box provides the following options in addition to the languages defined in the Dynamics Repository:
<ALL> - To generate client cache files for all defined languages.
<None - No Translation> - Use to generate client cache files to be used with Dynamics
sessions where the "<None>" has been used as the language or no language has been specified.
The persistent cache files are generated using the following naming convention:
ent_<Entity Name>_<Language Code>.d
Examples:
- ent_State_E.N-US.d: Cache file for the entity State for language code EN-US.
- ent_State_NONE.d: Cache file to be used for the entity State when no language has been specified..