I have completed a translation and am trying to save the target file and view it. It won't open and shows this error message: We're sorry. We can't open XXX file because we found a problem with its contents. Details: Xml parsing error. Location: Part:/word/document.xml, Line:2, Column: 3278
Can anyone help please?
That doesn't work for me, alas, because WordPad cannot import equations.
Does this solution that is so old really need to be used here? What version of Trados Studio are you using and what exactly is occurring for you? It might be better to create a new thread, explain your problem, and preferably provide a sample file that behaves this way.
If you don't know what part of the file is causing the problem keep splitting it in half and testing until you find one page, or even part of a page that won't open. Then anonymise the content if needed and share it. This is actually a remarkably quick process, even with very large files.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
I am using Trados Studio 2022 and am getting the exact same problem as the OP has described above. Four files out of a larger project are affected that I consistently cannot open after export because of this "XML parsing error". I have tried different Word versions to know avail. I have checked the tags in the files as advised by the OP and found nothing. Splitting the file as you suggest is no option since Trados Studio exports only full files, not parts of files. I have wasted half of this morning on that problem and found no solution.
I am using Trados Studio 2022 and am getting the exact same problem as the OP has described above.
I would be surprised if after 7 years you have the exact same problem. You only have the same headline message and this is why I suggested you create a new thread and share a sample.
Splitting the file as you suggest is no option since Trados Studio exports only full files, not parts of files.
I think you misunderstand me. Spitting the files is intended to find the problem and share it.
But having said that you could also use that technique to solve your issue because once you found it you simply remove that bit from the source file, translate it, save the target and then manually put the offending part back in again.
You could also try this:
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Following your point 1. above, I have managed to identify the problem.
The relevant DOCX files imported into Trados Studio 2022 had in common that their modification tracking was switched on in MS Word, and it seems that Studio is allergic to this function. Even when I did as recommended above, with no active TM installed, either, the above XML parsing error would occur when trying to open the exported target file. But switch off the tracking before import, and behold! the error is gone.
So there is clearly a bug in Trados Studio that prevents it from treating DOCX with active tracking. This is an issue that other users who hit on this error message should be aware of.
Following your point 1. above, I have managed to identify the problem.
The relevant DOCX files imported into Trados Studio 2022 had in common that their modification tracking was switched on in MS Word, and it seems that Studio is allergic to this function. Even when I did as recommended above, with no active TM installed, either, the above XML parsing error would occur when trying to open the exported target file. But switch off the tracking before import, and behold! the error is gone.
So there is clearly a bug in Trados Studio that prevents it from treating DOCX with active tracking. This is an issue that other users who hit on this error message should be aware of.
So there is clearly a bug in Trados Studio that prevents it from treating DOCX with active tracking. This is an issue that other users who hit on this error message should be aware of.
I think that's a little too simplistic. I just tried this a few times and don't have any problems at all. If you can provide a sample file that you have that causes this error I'd be happy to investigate it. I think there must be something a bit more specific to your file that is causing this.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
I may do that, yes. Where do I send it?
If you cannot isolate it and make the file safe to share in here then send it to pfilkin at sdl dotcom
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Translate
