Processing Top Texts

Use

The main aim of processing top texts is to create as many system standards with quality status A as possible for source texts that only need one translation which fits all possible contexts.

You are not aiming to create proposals for every source text in the top text objects. If a source text in a top text object is ambiguous, you should simply skip it.

This ensures that "easy" source texts, which can be translated automatically, are translated by automatic distribution. It also ensures that ambiguous source texts, which need actual translator attention, are translated correctly during manual translation and in accordance with the context of the object in which they occur.

Prerequisites

Before processing top texts, we recommend that you do as much research as possible about the subject area to be translated. Discuss and define as much terminology as you can, so that you can create as many proposals as possible with confidence while processing top texts.
Read the documentation on the proposal pool and automatic distribution carefully, so that you are aware of the consequences of distributing an unsuitable translation, and the work involved to correct it.
If you have a number of top text objects and more than one translator available to process them for a particular target language, decide on the objects that each translator will process. It can also be useful for all translators to discuss the source texts in the top text objects before deciding how to deal with them. This ensures that everyone translates using consistent terminology and style when manual translation starts, because all translators discussed these issues during top text processing.
You need to be able to create proposals with quality status A, to ensure that they have maximum distribution potential. Your translator profile must therefore contain authorization object PPQ1 with value 04.

Procedure

The graphics below illustrate the decision processes for top texts.

In the status bar above each source text, the system displays the frequency of the source text. So if you see the value 299 in the status bar, it means that:

If you can create a system standard with quality status A for this source text, you will save 299 lines of manual translation.
If you create an unsuitable translation as a system standard with quality status A for this source text, you could end up with 299 incorrect translations to correct.

If you want to process initial top texts, which means creating proposals for source texts for which no proposals currently exist, refer to the following graphic:

If you want to process upgrade top texts, which means checking existing proposals and changing their quality status to A if possible, refer to the following graphic:

For more information, see Changing the Quality Status of Proposals.

After you have finished processing a top text object:

Choose Save in the short text editor.
Choose Back (F3).
Process the next top text object.

Result

After top text processing is completed, an evaluation with automatic distribution must take place. You can then trigger manual translation.

Example

The table below contains a few sample source text that you might encounter in a top text object, along with our recommendations on how to proceed.

Source Language	Target Language	Source Text	Recommendations
English	German	Program SAPMTRAN	It is possible to define a unique translation that fits all possible contexts. Create Programm SAPMTRAN as a system standard with quality status A. This text occurs 400 times, so you have saved 400 lines of manual translation!
English	German	Change Document	It is not possible to define a unique translation that fits all possible contexts, because Change Document can be translated as Beleg ändern or Änderungsbeleg, depending on the context. Leave this line of the top text object blank, and proceed to the next line.
English	German	Application	Here it is not possible to define a unique translation that fits all possible contexts, because Application can be translated as Bewerbung, Anwendung, or Applikation, depending on the context. Leave this line of the top text object blank, and proceed to the next line.
German	English	Beschaffung	Here it is not possible to define a unique translation that fits all possible contexts, because Beschaffung can be translated as Procurement or Recruitment depending on the context. You are, however, sure that the translation Recruitment fits all possible contexts in the collections belonging to the domain PA (Personnel Management). Create Recruitment as a domain standard for the domain PA with quality status A.
German	English	Kostenstelle sichern	It is possible to define a unique translation that fits all possible contexts. Create Save Cost Center as a system standard with quality status A.
German	English	Parameter	Here it is not possible to define a unique translation that fits all possible contexts, because this German source text can be translated as Parameter or Parameters depending on the context. Leave this line of the top text object blank, and proceed to the next line.