Translation Status: Examples 

This topic gives you some examples of objects in the proposal pool and shows you the actions required to make the translation consistent with the proposal pool.

The above graphic shows an example of a text saved as a system standard. The example shows the status of the texts after saving.

Possible actions:

In this case, no action is required because the source text and the respective translations are consistent with the proposal pool.

In the above example, the first object Übersetzung has been translated as Translation tool. The second object Übersetzung has been translated as Translation. This is the status after saving.

Possible actions:

In this case, no action is required, as the exception is a text that is accepted by the proposal pool.

In the above example, the text has not been translated.

Possible actions:

Translate the source text or copy the proposal from the proposal pool, if one exists.

In the above example, the text Sich. in PC-Datei... has been translated as Save to PC file....

Possible actions:

To have the proposal pool accept this text, you must choose Confirm translation.

Alternatively, you can change the target text.

In the above example, the first text Liste has been translated as List. The second text Liste has been translated as Listing.

Possible actions:

An action is required. You can:

In the above example, the text Kursspanne has been translated in three different ways within the same object (here data element).

This is also shown by the figure 1 above the source text.

Possible actions:

Identical source texts within the same application should have the same translations.

If this is not possible, texts should be created as length variants. Different texts should only be created as exceptions if no other solution is possible.

See also:

Best Proposal

Length Variant

Translation Status