
You must be confident that the proposals you exported are of an acceptable translation quality. Otherwise you will just be spreading errors from one system to the next.
Why not organize a proposal pool cleanup in the source system before exporting proposals? For more information, see DEMS Objects for Quality Assurance .
To play it safe, you could export or import only those proposals with a specific quality status or higher, as long as you are confident that only experienced translators create proposals with high quality statuses.
The proposal pool file(s) that you exported must be available in a directory that the target system can access.
Before you import proposals, see Proposal Pool Transports and Exporting Proposal Pools for the benefits of importing existing proposals into a new system where you intend to translate and an explanation of basic concepts.
The system imports the proposals from the file in accordance with the criteria you specified.
Refer to the spool to see how many proposals have been imported.
|
Source Language: |
deDE |
|
|
Target Language: |
enUS |
|
|
Statistics |
Imported |
Total |
|
PP |
2.050 |
2.058 |
|
PPA |
40 |
40 |
|
PPX |
5 |
5 |
This means that the following proposals for source language German and target language English have been imported:
2.050 system standard/application standards.
8 of these proposals were not imported, due to the fact that proposals already existed for the source texts in question in the source system, and the Do Not Overwrite field contained an X when the import criteria were defined (step 9 of the Procedure above.
40 abbreviations
5 exceptions
The system creates an entry in table LXE_PP_IMP so that you have a permanent record of this import job.