
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, after it has been set up for translation, see Translation Tools for Translators (BC-DOC-TTL) .
This documentation is structured as follows:
|
Lists the four 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 externalization functions in transaction Translation Environment (LXE_MASTER) enable you to export the texts to be translated outside of the translation system. You can then import the translations back into the translation system. |
|
|
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. |
|
|
Provides information on how to select and assign collections correctly. You need to assign collections to translators before they can call up the objects that they need to translate in a worklist. |
|
|
Explains how you can collect translations in a transport request, in order to provide other systems in your landscape with translations. |