Translate
Symptoms/Context:
When importing a Return package (WSXZ) into WorldServer or (SDLRPX) TMS, the user gets an error message that points to the SDLXLIFF file being damaged.
Root Cause:
A Return package contains a damaged SDLXLIFF file that produces an error when imported to WorldServer, or shows as unable to be uploaded in TMS.
In WorldServer, if the error is ignored, the same error appears when the Task gets to the "Save" step or when the Task is opened in Browser Workbench and saved.
In TMS, the task will not be uploaded and will revert to the previous version of the file
Often the resolution is to re-create an "healthy" Return package based on the original export Studio package.
In WorldServer, if the error is ignored, the same error appears when the Task gets to the "Save" step or when the Task is opened in Browser Workbench and saved.
In TMS, the task will not be uploaded and will revert to the previous version of the file
Often the resolution is to re-create an "healthy" Return package based on the original export Studio package.
Resolution:
Use the original export package (before translation) and the WSXZ Studio Return package or the SDLXLIFF file(s) inside the Return package that caused the error. Once you have the needed files/packages, follow these steps:
1- Rename the Return package to *.zip and extract to to access the problematic SDLXLIFF file
2- Open the original WSXZ Studio package exported before translation in SDL Trados Studio.
3- In case you receive an alert about Dependency File when opening the package, download the source file, click Yes and browse to the source file. See also article 000001292 - Task Upload Error - Dependency file not found
4- Now go to Batch Tasks and select Apply Perfect Match.
5- Click Next
6- Select the option Use the original translation original and status and click on Add/Matching Previous document to add the SDLXLIFF file from the translator's Return package (see #1) by browsing to it and selecting it. Click Next.
7- Click Finish
8- Now your bilingual file has been translated based on the SDLXLIFF file from the translator, keeping the same segment status.
IMPORTANT: in Studio, do a File/Save target as... to make sure that a target file can be created correctly in SDL Trados Studio. IIt is important that the target file is created successfully in SDL Trados Studio.
9- Create a Return package with the fixed and translated file and import the package into WorldServer.
10- The import should be successful.
If the Task is in Autoerror at the Save step in WorldServer, complete the Autoerror.
A video is available in the SDL Trados YouTube channel:
Working with PerfectMatch 2.0
1- Rename the Return package to *.zip and extract to to access the problematic SDLXLIFF file
2- Open the original WSXZ Studio package exported before translation in SDL Trados Studio.
3- In case you receive an alert about Dependency File when opening the package, download the source file, click Yes and browse to the source file. See also article 000001292 - Task Upload Error - Dependency file not found
4- Now go to Batch Tasks and select Apply Perfect Match.
5- Click Next
6- Select the option Use the original translation original and status and click on Add/Matching Previous document to add the SDLXLIFF file from the translator's Return package (see #1) by browsing to it and selecting it. Click Next.
7- Click Finish
8- Now your bilingual file has been translated based on the SDLXLIFF file from the translator, keeping the same segment status.
IMPORTANT: in Studio, do a File/Save target as... to make sure that a target file can be created correctly in SDL Trados Studio. IIt is important that the target file is created successfully in SDL Trados Studio.
9- Create a Return package with the fixed and translated file and import the package into WorldServer.
10- The import should be successful.
If the Task is in Autoerror at the Save step in WorldServer, complete the Autoerror.
A video is available in the SDL Trados YouTube channel:
Working with PerfectMatch 2.0
Reference