After the import of a Return package that contains content in Reviewed or Signed off status in Trados Studio, when opening the Task in Browser Workbench, all (or some) segments have the green flag pointing to the Reviewed status, but the percentage is set to 0% and to Not Translated or are in grey color. Also, when filtering the segment view to Not Translated, those segments are displayed although they should be in Reviewed status. This cases tasks/files including those segments to be detected as not-translated by the QA Check Workflow step and/or the Test If All Segments Translated Automatic Actions, meaning that the Task cannot proceed in the Workflow, but is sent back to translation for update. Also, the translation of those segments is not updated in the TM. |
This issue is caused by defect CRQ-12097. The defect has been fixed with a cumulative update in WorldServer version 11.3.7, and 11.4.3.171, and a hotfix in 11.5.0 and later WorldServer versions. In versions where the issue is not fixed yet, there are 3 possible workarounds: 1- MANUAL: enter a manual change in the Machine Translated segment in Studio (i.e. add and remove a space) and confirm it. By doing so, the manual change will be detected and the segment status origin will be changed to Origin=Interactive, which is recognized by WorldServer. The previous origin is preserved, but the current origin and status is changed to interactive, which is recognized by SDL Worldserver as translated or reviewed. <sdl:seg id="18" conf="ApprovedTranslation" origin="interactive"><sdl:prev-origin origin="nmt" origin-system="SDL Machine Translation Cloud provider"> Once the manual change is done, create a new Return package and import it to Worldserver 2- Alternatively, you can do the same directly in Browser Workbench: filter out the segments in Not translated status. Those are the ones causing the issue. As explained above, you will see that they have a segment status, but the field is greyed out, which means that they are not considered translated. In Browser Workbench, add a manual change to the target segment (like adding and removing a space) and click on Save. The segment will be updated as translated. Repeat this for all affected segments. Once this is done, the TM will be updated accordingly. Complete the Translate step (or Review or any other human step). Any automatic step that checks if there are untranslated segments won't find any anymore. 3- To change the status/origin of multiple segments in one or multiple files in Studio, you can use the Integrated Segment Actions Plug-in from the SDL Language Solutions AppStore and install it for your version of Trados Studio. Once installed, you can run it by right-clicking on the project's name in Studio and clicking on Segment Actions. The Segment Actions window will open up. Here you can select the segments that you want to change. For instance:
and after running the tool: |
This issue is caused by defect CRQ-12097. A Hotfix has been provided in versions 11.3.7, 11.4.3, 11.5.1 and has been permanently fixed in version 11.6. Those segments have been pre-translated in SDL Trados Studio using SDL Language Cloud Machine Translation. This is how such segment displays in SDL Trados Studio: The status is Reviewed and the origin is NMT (Neural Machine Translation). If you open the translated SDLXLIFF file in Notepad ++, the segment displays as follows: <target><mrk mtype="seg" mid="18">AC devre kesiciler</mrk></target><sdl:seg-defs><sdl:seg id="18" conf="ApprovedTranslation" origin="nmt" origin-system="SDL Machine Translation Cloud provider"> Note: depending on the type of LC Machine Translation used (statistical/adaptive or neural), the origin could also be amt. The same behavior applies for amt segments as with segments translated with neural Language Cloud machine translation ("nmt"). They display as untranslated, although the segment status might be Translated or Reviewed in Browser Workbench and the TM is not updated. After import of a Return package where segments have been translated with Adaptive Language Cloud machine translation, such segments display the same way as nmt segments like this: In Trados Studio, the segment displays as follows: When opened in Notepad ++, the segment's origin is marked as amt: <sdl:seg-defs><sdl:seg id="xxx" conf="ApprovedTranslation" origin="amt" origin-system="SDL Language Cloud Machine Translation"> Worldserver does not recognize origins like amt and nmt and considers the segments as not translated. |