Dear Community, I am trying to import a translation into Worldserver, but it keeps coming back. Everything has been confirmed in SDL, but Worldserver indicates that not everything has been confirmed. How can I solve this?
Dear Community, I am trying to import a translation into Worldserver, but it keeps coming back. Everything has been confirmed in SDL, but Worldserver indicates that not everything has been confirmed. How can I solve this?
Hi Doctec, what the version of WordServer into which the Return package has been imported into? Also, do you get any error when importing/uploading the Return package? Last, can you add a screenshot of a segment as displayed in Studio and as displayed in WorldServer after the import? Thanks, Caterina
Hi Caterina, the version of Worldserver is 11.4.2.127. No we don't get any errors when importing the return package. Here is a screenshot of Studio
And here is a screenshot of Worldserver:
Many thanks in advance!
Hi Doctec, what the version of WordServer into which the Return package has been imported into? Also, do you get any error when importing/uploading the Return package? Last, can you add a screenshot of a segment as displayed in Studio and as displayed in WorldServer after the import? Thanks, Caterina
Hello DocTec, the problem is that you have exported the project/tasks in XLIFF format instead of the WSXZ WorldServer Studio package format. XLIFF format should be avoided for WorldServer environment with live TM such as the one you are importing into. The main issue is that the TM does not get updated when using XLIFF files.
This article explains the issue in details:
https://gateway.sdl.com/apex/communityknowledge?articleName=000015031
The workaround for your project/task (since it contains only 23 segments) is to manually add a small change to each target segment in Browser Workbench (like adding and removing a space) and then click "Save". The segment status and the TM will be updated. Do this for each segment.
To avoid this issue to happen again, always export in WSXZ package format and work with that format only. In case you have not worked with WSXZ packages before, this article gives some guidance:
https://gateway.sdl.com/apex/communityknowledge?articleName=000002706
I hope this helps you!
Hi Caterina, many thanks for your answer, but the project is very big. The screenshot was only one file. Is there another solution?
If the project's tasks are still assigned to you, export them as a WSXZ package, open in Studio, confirm each segment in each file, create a Return package and import back.
Yes, it is still assigned to us. The segments are already confirned. Do I have to confirm them all again one by one?
Hi again, is it possible for you to create a Support case and provide the Return package you are importing? I think it would be good to exchange the data to investigate further. I have looked at the project in WordServer (we have access to it) and you have exported in WSXZ format, so the issue is not the export format (my misunderstanding). So we need to look at your Return package to understand why the segment status displays wrongly. You can also ask your customer to create a case on your behalf and ask them to share the Return package with us. Which Studio version are you using?
I will ask our customer. We are using studio 2021. Many thanks for your answers.
How have the files be translated in Studio? Have you maybe applied some local TM or a server TM? What is the difference between the way you have translated the affected tasks and then ones that did not have the issue? I have exported Task 72 to a new WSXZ package and the segment status in Studio appears odd, especially that 0% in combination with origin "WorldServer Translation" memory: