This documentation describes how to set up a system for translation, and how to coordinate a translation project.
For information on how to translate in an SAP system, see Translation Tools for Translators (BC-DOC-TTL).
This documentation is structured as follows:
|
Lists the five possible translation strategies you can use to translate objects in your system. Explains the settings you need to make to enable multiple languages to work in the system in which you want to translate. |
|
|
The UI text space calculator and pseudo-translation enable developers to assure internationalization aspects of their developments before translation even starts, resulting in better user interfaces in all languages and efficiency gains during the translation cycle. |
|
|
The translation object detective makes it far easier for you to find translation objects that you need to edit in transaction SE63, so that you can change or correct texts that appear on the user interface. |
|
|
The externalization functions in transaction LXE_MASTER enable you to export the texts to be translated. You can then import the translations into the system. |
|
|
On-the-fly translation allows you to create a temporary worklist in the system on the basis of an object list, transport request, transport object, collection (ABAP package), or local list without setting up the translation environment first. |
|
|
Provides information on how to define the translation environment in accordance with how and what you want to translate. |
|
|
After defining the translation environment, you need to scan the objects requiring translation to calculate their translation status. This section describes how to create object lists and evaluations that place the objects requiring translation in worklists and also create detailed statistics on the translation workload. |
|
|
Explains how to use the statistics to monitor the translation workload and how to use them as a reference when assigning collections, to ensure that each translator has a similar number of lines to translate. |
|
|
Describes how you can use DEMS objects to drastically reduce the translation workload before the translators start to translate. |
|
|
Explains the settings you need to make so that short text lines are translated automatically by high-quality proposals in the proposal pool, which is the translation memory for short texts. |
|
|
Provides information on how to select and assign collections correctly. You need to assign collections to graphs when setting up the translation environment, and to translators before they can call up the objects that they need to translate in a worklist. |
|
|
Explains various functions that enable you to coordinate translation more effectively. |
|
|
This section explains the concept of local lists, provides examples of situations in which they can be useful, and describes how to create and use them. |
|
|
Explains how to use transaction TPMO, which is a tool for monitoring translation performance. Coordinators can use the translation performance monitor to monitor the overall workload processed during a translation project by one or more target languages. |
|
|
Explains how you can collect translations in a transport request, in order to provide other systems in your landscape with translations, and how to transport translation data (that is, proposal pools and fingerprints) and translation settings from one system to another. |
|
|
The Proposal Pool Analysis Tool (transaction PPAT) enables you to analyze the contents of the Proposal Pool according to a variety of criteria for one or more combinations of source and target language. |