Translation Scenarios

It is possible to both prepare model content in alternative display languages for certain user circles and model the entire model into another model language other than German or English.

Core Translation Scenarios

Scenario 1: Use Display Languages for Presentation or Documentation

You wish translate content which exists in the model language based on a model and its configuration into other display languages for presentations or documentations.

This is always recommended if the model users are not familiar with the model language or if the model content needs to be made available in various languages due to user requirements.
Scenario 2: Use Alternative Model Language

You wish to start a new model with a model language other than German or English.

Please note that English as model language is of particular advantage in an international environment, as it is used as a foreign language in many countries and supports modeling languages (UML, BPM etc.) as recognized standards in English. This means that e.g. coordination and translation of numerous terms and definitions for this standard is not necessary. These terms may be extensively used in the technical model content.

Note

A professional external translation will use a database (translation memory) which recognizes identical source texts as a previously translated segment and will automatically translate this segment.

Qualitative professional translations can be achieved by using a defined terminology (term base).

Scenario 1: Use Display Languages for Presentation or Documentation

Starting Point

You wish to use content which exists in the model language in other languages for presentation and documentation purposes.

The model consists of the metamodel, configuration content and model content, which means that all of these aspects should be translated if you require a complete presentation in a display language.

A partial translation (model content in particular) may be sufficient for presentation and documentation of certain aspects of the complete model.

It is a good idea to at least select the standard model language English as the exporting language. It is also recommended that you use English as your source language for a translation due to the modeling standard being in this language.

Note

The starting point for a model in a display language is a model in the modeling language, preferably English.

Prerequisites

The model administrator needs to set the display language required.

This then creates a container for the translations in this language.

All users in the model can then change between the model language and display language.

Content must be translated before it can be shown in the display language. If a translation does not exist, then the logical name is used for the model content. This is normally the model language for the German and English model languages.
Users that wish to translate model content internally or externally require the Translate Model Elements privilege.

Users with the Translate Model Elements privilege can use the export and import function in the Manage Languages backstage view to translate the entire model externally. There are various interface formats available for this.

You can also use the translation window to directly translate model content or use a web service, if required.
The license administrator must set up the web service (which may incur a fee) in the administrator program before it can be used for automatic translation.

Translating the Metamodel

Context

The metamodel is the same for all Innovator models within an Innovator version; this means it only needs to be translated once per language. Translated content can then be used by all other models within the Innovator version and must simply be imported.

The metamodel provides e.g. the names of element types and texts with their descriptions.

Attention

You cannot put a "X" for the metamodel in the Not to translate column in the translation file.

How to proceed

In the Manage Languages backstage view in the Translation section, click on Export.

The Translation File Creation Wizard appears.
Select The meta model to adopt translations in the translation file for all elements in the metamodel.

Automatically jump to step Select the Languages.
Select the source language and desired target language.

Automatically jump to step Format and State.
Select the file format for the translation file and activate all translation states.
Confirm with Next.

Automatically jump to step Ready to Create the Translation file.
Check the settings and select Finish to create the translation file with these settings.

The translation file is created and the standard dialog for saving a file appears.
Save the file and send it to your translator.
All content in the file in the Property Value (<source language>) should be translated into the Property Value (<target language>) for all target languages.
Click on Import in the Translation section in the Manage Languages backstage view to import the translated file into a model so that you can use the translations in all target languages.

The standard dialog for opening a file appears.
Select the translation file and confirm with Open.

All elements found in the file are given the translations in the languages found.

Translating the Configuration

Context

The configuration includes configuration content, e.g. stereotype names, property names and label values.

You only need to translate the configuration for models with the same configuration once (model templates and customizations in the configuration). Translated content can then be used by all other models with the same configuration in the same Innovator version and must simply be imported.

You can limit the translation to the profiles which are actually used by filtering the translation file according to Namespace of Element

Attention

You cannot put a "X" for the configuration in the Not to translate column in the translation file.

How to proceed

In the Manage Languages backstage view in the Translation section, click on Export.

The Translation File Creation Wizard appears.
Select The configuration to adopt translations in the translation file for all elements in the configuration.

Automatically jump to step Select the Languages.
Select the source language and desired target language.

Automatically jump to step Format and State.
Select the file format for the translation file and activate all translation states.
Confirm with Next.

Automatically jump to step Ready to Create the Translation file.
Check the settings and select Finish to create the translation file with these settings.

The translation file is created and the standard dialog for saving a file appears.
Save the file and send it to your translator.
All content in the file in the Property Value (<source language>) should be translated into the Property Value (<target language>) for all target languages.
Click on Import in the Translation section in the Manage Languages backstage view to import the translated file into a model so that you can use the translations in all target languages.

The standard dialog for opening a file appears.
Select the translation file and confirm with Open.

All elements found in the file are given the translations in the languages found.

Translating Model Content

Context

Model content includes all model content created by the model template or modeler, e.g. names of model elements, values of properties and specification texts.

Model content must be translated individually for every model.

We recommend a professional external translation to ensure consistent translation for technical context of models.

Attention

If a model element is marked with an "X" in the Not to translate column in the translation file, then all translations in all languages will be deleted and the logical name will be used.

How to proceed

If you wish to translate using the translation file, then proceed as described above for the metamodel and configuration, but make the selection in the Translation File Creation Wizard based on your requirements.

The rest of the process is identical.

(also see "Translation File Creation Wizard")
If you wish to translate in the model using the translation window, then select the model elements to be translated and enter the name, value and text.

You can use a web service for automatic translation.

(see "Translation Tool Window" and "Translation editor for a specification text")

Distributing Translations

Once translations have been completed in one model, they are usually also used in other models (this is certainly the case for the metamodel and configuration and may also apply to model elements).

To do this, import the translation files to the Translation section in the Manage Languages backstage view as described above. You require the Translate Model Elements privilege.
Verification should be carried out in the model before the translation is distributed. Any corrections can be exported in a translation file. Correction is not always possible in the model as certain elements (e.g. in the metamodel) cannot be reached. Correction can then be carried out directly in the translation file.
The model administrator can also export the language container in the output model in the Model Contents tool window in the Administrative Contents view using the Filter Translations for
- Metamodel (<language> [Meta Model Translation]),
- Configuration (<language> [Configuration Translation]) and
- Model content (<language> [Model Translation])
using the Import/Export>Export>Model Fragment>Export Selection... command.

Each user can then import these model fragments into any number of other models with Import/Export>Import>Model Fragment>Import Model Fragment....

This always overwrites any existing translations in the target models.
You can select which translations you wish to use for individual model elements in the Align Models tool window.

Scenario 2: Use Alternative Model Language

Starting Point

You wish to model a new model into a model language other than German or English.

If you wish to change the modeling language in general, then create and distribute the appropriately translated model templates.

A model is made up of the metamodel, configuration content and model elements at the very least which can be found within a model template. All of these components must be translated for a complete model or relevant model templates.

Model content is "translated" into another language by creating these elements in the model language.

Note

You require an empty model (preferably English) from a model template included within the scope of delivery for a model template in the model language.

Attention

Changing the model language is only appropriate when starting modeling, so that you can use language-specific word wrapping in diagrams and spell check in specification texts.

Making changes at a later stage will mean that you will have to manually rename numerous model elements and may need to retranslate profile and metamodel content.

Prerequisites

The model administrator needs to set the model language required.

This then creates a container for the translations in this language.

From this point, all users then model in this language.

If a translation does not exist in the model language, then the interface language (preferably English) is initially used for metamodel and configuration content, then the logical name; model elements always use the logical name if a translation does not exist.
Users that wish to translate model content externally require the Translate Model Elements privilege.

Users with the Translate Model Elements privilege can use the export and import function in the Manage Languages backstage view to translate the entire model externally. There are various interface formats available for this.

Translating the Metamodel

Context

The metamodel provides e.g. the names of element types and texts with their descriptions.

Attention

You cannot put a "X" for the metamodel in the Not to translate column in the translation file.

How to proceed

In the Manage Languages backstage view in the Translation section, click on Export.

The Translation File Creation Wizard appears.
Select The meta model to adopt translations in the translation file for all elements in the metamodel.

Automatically jump to step Select the Languages.
Select the source language and desired target language.

Automatically jump to step Format and State.
Select the file format for the translation file and activate all translation states.
Confirm with Next.

Automatically jump to step Ready to Create the Translation file.
Check the settings and select Finish to create the translation file with these settings.

The translation file is created and the standard dialog for saving a file appears.
Save the file and send it to your translator.
All content in the file in the Property Value (<source language>) should be translated into the Property Value (<target language>) for all target languages.
Click on Import in the Translation section in the Manage Languages backstage view to import the translated file into a model so that you can use the translations in all target languages.

The standard dialog for opening a file appears.
Select the translation file and confirm with Open.

All elements found in the file are given the translations in the languages found.

Translating the Configuration

Context

The configuration includes configuration content, e.g. stereotype names, property names and label values.

You only need to translate the configuration for models with the same model templates and of the same Innovator version once.

You do not need to translate your own profiles which you create directly in the model language. You only need to translate profiles included by MID within the scope of delivery into the model language.

You can limit the translation to the profiles which are actually used by filtering the translation file according to Namespace of Element You can remove unused profiles in the configuration.

Attention

You cannot put a "X" for the configuration in the Not to translate column in the translation file.

How to proceed

In the Manage Languages backstage view in the Translation section, click on Export.

The Translation File Creation Wizard appears.
Select The configuration to adopt translations in the translation file for all elements in the configuration.

Automatically jump to step Select the Languages.
Select the source language and desired target language.

Automatically jump to step Format and State.
Select the file format for the translation file and activate all translation states.
Confirm with Next.

Automatically jump to step Ready to Create the Translation file.
Check the settings and select Finish to create the translation file with these settings.

The translation file is created and the standard dialog for saving a file appears.
Save the file and send it to your translator.
All content in the file in the Property Value (<source language>) should be translated into the Property Value (<target language>) for all target languages.
Click on Import in the Translation section in the Manage Languages backstage view to import the translated file into a model so that you can use the translations in all target languages.

The standard dialog for opening a file appears.
Select the translation file and confirm with Open.

All elements found in the file are given the translations in the languages found.

Translating Model Content

Model content is "translated" into another language by creating these elements in the model language.

Distributing Translations

Verification of the translated model should be carried out before the translation is created and distributed. If certain corrections are not possible in the model because certain elements (e.g. in the metamodel) cannot be reached, then they can be corrected directly in the translation file that has been exported again and then this can be reimported.
The language-specific model template can be created in the model language and then distributed once the empty model in a model template has been translated and any model structures required have been created.

(see "Preparing and Using Model Templates")
The model administrator can also export the language container in the output model in the Model Contents tool window in the Administrative Contents view using the Filter Translations for
- Metamodel (<language> [Meta Model Translation]) and
- Configuration (<language> [Configuration Translation])
using the Import/Export>Export>Model Fragment>Export Selection... command.

Each user can then import these model fragments into any number of other models with Import/Export>Import>Model Fragment>Import Model Fragment....

This always overwrites any existing translations in the target models.