We have segmented a DOCX file using the Microsoft Word 2007-2016 File Type on a WorldServer 10.4.5. environment. After translation, the target files are only partially translated. A big part of the file is untranslated. There was no error at segmentation, Save, export or import. The file displays as fully translated in Browser Workbench and the Translation Memory has been updated correctly. The same issue occurred on another WorldServer 10.4.5 customer site using the Custom XML (Embedded Content Processor) Studio File Type |
The issue is solved in later versions of WorldServer using the same file type. As a workaround, 1- export the translated Task from WorldServer to a WSXZ Studio package. 2- Rename the package to ZIP and extract it 3- Download the source DOCX file from WorldServer 4- Open the source DOCX file as a standalone file in SDL Trados Studio 2017 or 2019, selecting the same source and target language as in WorldServer. 5- Run a Apply PerfectMatch Batch using the translated SDLXLIFF file exported from WorldServer as described here. 6- Run a tag verification and fix any tag issues 7- Search for untranslated segments and translate them using the SDLXLIFF file from the Return package (you can open it in a second window in Studio) 8- Finally, in SDL Trados Studio, create a target file out of your re-translated file and confir it is fuly translated. 9- Use that file for delivery or replace the target file in Explorer (partially translated) with the one created in SDL Trados Studio. |
Some translated content cannot be written correctly in the target DOCX file due to a defect in the version of the Microsoft Word 2007-2016 File Type available in WorldServer 10.4.5. For the Custom XML (Embedded Content Processor) Studio File Type, there must have been a silent error on the import as the TM was updated properly and only the first portion of the target asset had translated content, the rest was in English. Possibly a defect in WorldServer 10.4.5. |