Nicola Ormshaw

What version of Studio are you using, and is it possible to see the files?  If there is a bug in the currently supported versions of the product we can submit it for investigation and resolution.  You can send them to pfilkin@sdl.com if this is ok?

Nicola Ormshaw

Thank you for sending me the email with your stacktrace.

A couple of things then:

1. I can’t help efficiently without the files, so can only guess where the problem lies
2. You need to update your version of 2017. The current version is:
   SDL Trados Studio 2017 SR1 - 14.1.10018.54792
   SDL MultiTerm 2017 SR1 - 14.2.8.55461
3. 2017 isn’t actually supported anymore, so if you did provide the files and it turned out to be a bug in Studio we would only resolve it in the current supported versions of the software

Hopefully, the update will help you.  Otherwise the best advice I can offer is this:

1. Try to see if there is a problem with the files
   1. Open one that failed and verify it fails on its own
   2. Split the ODT into two, test both halves.
   3. If one half fails and the other succeeds then split the one that failed and repeat
   4. Repeat this process until you find the part of the file that’s causing the problem. Then you may be able to remove that part from the source and replace it afterwards
   5. If both halves fail then there will be nothing we can do without seeing the files. Although you could test them yourself with the trial version of 2021 and see if the latest version handles the files at least.

Thanks Paul. In the end, I found that I could open the individual odt. source files (not the ones inside the package, but by downloading the individual source files separately) and translate them. Didn't realise 2017 wasn't supported any more so may look into upgrading.

Thanks for coming back and confirming Nicola Ormshaw...