Proposal Pool Transports

Whenever a new translation system is set up or a development (or part of a development) moves from one translation system to another, you must transport the proposal pool for each source and target language combination from the source system (the system previously used to translate the development) to the new translation system (target system).

Reusing the existing proposal pools in this way has the following benefits:

• The target system contains proposals for translations that already exist. The source text lines in question therefore have the translation status Translated and do not need to be edited again. This avoids unnecessary translation work.

• Any proposals matching the criteria for automatic distribution will be used to automatically translate any new and modified lines in the target system, again saving translation work.

• This ensures that the same translations are used in all your translation systems, ensuring consistent, high-quality translations.

In short, transporting proposal pools from one translation system to the next saves time, money, and improves translation quality.

A suitable proposal pool exists for the required source and target language combination(s). For example, you have translated into each of the target languages in question and have created proposals in the proposal pool while you translated.

You can transport a translation system's entire proposal pool to another translation system, or you can transport just part of a proposal pool.

You can restrict the proposals that you transport according to the following criteria:

• Date on which the proposals where last changed

  Example

  You choose to export only proposals created or changed since January 2007, due to the questionable quality of proposals created before that date.

• Proposals for specific objects only

  Example

  You can use an object list as the basis for a proposal pool transport. This means that the system only exports proposals for those source texts that appear in the objects that this object list contains.

You need to perform the following steps for each source language and target language combination

1. Check that proposals actually exist for the source and target language combination. If not, then you have nothing to transport!

2. Export the proposal pool(s) from the source system.

3. Import the proposal pool(s) into the target system.

Transaction LXE_MASTER enables you to transport proposals in different ways:

• If you want to import proposals that were exported from a system on Basis Release 6.20 SP24 or lower, you need to import proposals with an old format.

• If you want to transport proposals via an RFC connection, you need to copy proposals between systems.

• If you want to perform a standard proposal pool transport, you need to export and then import translation data.

Importing Proposals with an Old Format

Copying Proposals Between Systems

Exporting Translation Data

Importing Translation Data