Michael Beijer 

The main benefit of the Bilingual Word Review file was always that people who don't have a CAT tool and who are unable or unwilling to use one can still review the translation. If you are only using it for export/import, why not use the files that the very good app XLIFF Manager generates?

 Michael Beijer Paul Caterina Lazzarini Jesús Prieto Daniel Hug 
In my experience, this feature works very well and reliably.
You don't need to make changes using Track Changes. Changes made without Track Changes are also imported. I haven't used this feature in a long time, but I checked it today (Trados Studio SR1 CU3) and can confirm that this is the case.

Important: the file you use for the update must be the same file that was generated by Trados. Copying text/content from the original DOCX file to the new one does not work. This can be seen in the examples below. The original DOCX exported from Trados Studio has an additional CustomXml folder with an XML file that contains the identifiers and hashes of the source and target segments.

And now everyone knows what problems can arise:
- The SDLXLIFF file was changed in Trados Studio after the Bilingual Review file was generated (the hashes have changed, the update will fail)
- The SDLXLIFF file has already been updated using the Bilingual Review file (the hashes have changed, the update can only be performed once)
- etc.

I have used Bilingual Update in a very unusual way many times. For example, I created the original bilingual review file in Trados, and then pasted the comparison of changes obtained from two different documents into the 4th column, and the function always worked. It is important to remember that:
- You cannot make changes to the Trados Studio project in the meantime,
- You must have the same DOCX file generated in Trados Studio with a list of segment IDs and hashes
- The update can only be done once (because the hashes will change)







Dariusz Adamczak (Post-edit a CAT)

 Michael Beijer Paul Caterina Lazzarini Jesús Prieto Daniel Hug 
In my experience, this feature works very well and reliably.
You don't need to make changes using Track Changes. Changes made without Track Changes are also imported. I haven't used this feature in a long time, but I checked it today (Trados Studio SR1 CU3) and can confirm that this is the case.

Important: the file you use for the update must be the same file that was generated by Trados. Copying text/content from the original DOCX file to the new one does not work. This can be seen in the examples below. The original DOCX exported from Trados Studio has an additional CustomXml folder with an XML file that contains the identifiers and hashes of the source and target segments.

And now everyone knows what problems can arise:
- The SDLXLIFF file was changed in Trados Studio after the Bilingual Review file was generated (the hashes have changed, the update will fail)
- The SDLXLIFF file has already been updated using the Bilingual Review file (the hashes have changed, the update can only be performed once)
- etc.

I have used Bilingual Update in a very unusual way many times. For example, I created the original bilingual review file in Trados, and then pasted the comparison of changes obtained from two different documents into the 4th column, and the function always worked. It is important to remember that:
- You cannot make changes to the Trados Studio project in the meantime,
- You must have the same DOCX file generated in Trados Studio with a list of segment IDs and hashes
- The update can only be done once (because the hashes will change)







Dariusz Adamczak (Post-edit a CAT)

Thanks for all the info!

By the way, Supervertaler can currently successfully import, translate, and export bilingual Trados review files! As long as the user follows a few rules, outlined in my screenshot above. It took a couple of iterations, but Claude Coe nailed it in the end.

I have also nearly completed a functional Trados package import/exporter that exports Return Packages identical to those produced by Trados.

See: https://supervertaler.com/changelog

PS: Supervertaler runs on Windows, macOS, and Linux and is completely free and open-source!

Michael Beijer 

I know these files may drive you crazy. So I have a method which works for me always, in case the import back is failing.

My steps:

• When the import of a bilingual review file fails, I store the revised file in a separate folder and keep it unchanged
• Tracked changes do not really matter, if there are some in the revised file and you need to see them in Trados Studio, keep them. Otherwise you can also accept them in Word
• Make sure there are no line breaks in the revised file. Should there be any, remove them
• Delete the originally exported file for bilingual review
• Export the sdlxliff file again
• Open the newly exported file
• Switch track changes off
• Open the previously revised file
• Switch track changes off
• Remove the first row from the table there
• Select the target column. The easiest way is to place the mouse cursor above the column. When it changes the shape clicking selects the whole column
• Paste the copied content by clicking in the first text cell of the newly exported file in the target column
• Save this file and try to import
• This should work

Otherwise TS might give you an error and point you to the row, where the error appears. Go to that column in the Word file and check, if there has been any tags. Most probably there were tags and the formatting of these tags has been applied to surrounding text or simply changed. If you, you need to recreate this cell using the revised content and the content from a newly exported file (you need to export it again for this).

I know this is quite a big effort, but usually it works.

The exported file may not be changed in formatting, especially you may not touch the first and second column. Only working in the target column is allowed.