Start of Content Area

Function documentation Translation Graphs  Locate the document in its SAP Library structure

Use

Translations are always from a source language to a target language. Various criteria, such as the source language from which your translators work, influence your choice of source language. It is entirely possible for translations into various target languages to be written from different source languages. If you need texts to be translated into French, for example, it may be easiest for you to find translators who use German as their source language. If you need texts to be translated into Korean, however, you may only be able to find translators who use English as their source language.

There is also the language in which your developers work. This is the original language of an object. It can be identical to the source language of a translation, but it does not have to be. If objects are translated into a target language from a source language in which the objects are not developed, the translators who work into this target language must wait until the translation into their source language is available.

This results in different combinations of original language, source language, and target language in a single translation system. All of these translation directions are grouped together in a translation graph. Worklist runs cannot be generated for translation until appropriate translation graphs have been defined.

Example

Your translation system, Translation1, is used to translate texts into English, German, Italian, and Japanese. Some of the objects are developed in German, and some of them are developed in English. German and Japanese are translated from English, while Italian and English are translated from German. This means that the objects developed in German can be translated straight into Italian. However, the Italian translators must wait for objects developed in English to be translated into German first.

You define the following translation directions:

English

Original language German -> source language German -> target language English

German

Original language English -> source language English -> target language German

Italian

Original language German -> source language German -> target language Italian

Original language English -> source language German -> target language Italian

Japanese

Original language German -> source language English -> target language Japanese

Original language English -> source language English -> target language Japanese

These translation directions are grouped together to form the translation graph.

In some systems, it is possible for the source language of a particular target language to differ from one project to another. For example, the collections that belong to the project Bank1 could be translated from German into Italian, whereas the collections that belong to the project Tradeshow1 could be translated from English into Italian. In that case, different translation graphs are required for the projects Bank1 and Tradeshow1.

Graphs also enable you to separate collections that need to be translated in different projects.

Integration

The translation graphs determine which collections are taken into account when object lists are generated, and when evaluations are run. You can also use them as a selection criterion when assigning or displaying collections.

Prerequisites

Your translator profile includes the authorization GRAP with the value 02.

You have ensured that the languages defined as source languages have been set up as target languages in the translation system.

Features

The number of projects in your translation system with different source language-target language combinations determines the number of translation graphs you require. You also need an empty translation graph as a lock graph.

Activities

You assign collections to the translation graphs you have defined in accordance with their translation direction. This releases the collections for translation, which means they are now included in worklist runs and automatic distribution. If collections are not assigned to any translation graph, they do not exist as far as the translation environment is concerned. If you want to exclude certain collections from translation deliberately, assign them to an empty translation graph. This is a graph for which no translation directions have been defined. If you do not want to release collections for translation yet, but require statistics on them for expense analyses, define a monitoring graph and assign the collections to it. However, do not assign these collections to any translators.

 

 

 

 

 

 

End of Content Area