Dear All,
I have translated a large file and finalized it so my TM is up to date. However, I cannot open the generated target or export file based on my translation.
I then tried to import the translatable file (after having renamed it), in order to retranslate it based on my TM, but this gives the same result.
All tips are welcome!
Hello,
I get this error message: 
Look a bit like you are translating an XML file?
Can you open the source Word file without any problems? Did you run tag verification in Trados Studio? Any segments merged over paragraph boundaries? What purpose shall the bilingual review file have? What kind of error message do you want to retrieve? Any error message from Word when trying to open the translated file there? Which Word version do you have?
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Parallel discussions!
Docx files are XML files zipped together I believe. The character that causes the issue is a Start of Text character, which is not visible or printable and it's not allowed in XML files. (Against XML standard.) So that's the problem as far as I can see. I have to think about a good solution, unless Jerzy Czopik comes up with one first!
From my experience I've never seen a Word file including such character. However, such characters do appear sometimes in sdlxliff files and come for example from old TMs or from user names or other attributes, possibly when a TM was converted via TMX from other format. I suppose she was trying to open the translated sdlxliff file, where this error was caused.
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
Yes, the source Word file opens completely normally, without any issue. I indeed ran the tag verification and fixed/ignored the issues mentioned there.
I indeed merged some segments, possibly over paragraph boundaries. The bilingual review is not necessary, I only tried this to check what error message would come out.
The Word version we have is Microsoft office 365 - version 2510 (build 19328.20266).
Is there an indication of the segment that's causing the issue?
Would be interesting to see which issues the verification process found you ignored...
Here's the overview of the messages I ignored : 
Yes, makes sense. That control character must have sneaked in through some insertion process. I don't think you can enter it manually. You could search through the DOCX for that character and replace it with a space or delete it, but that requires some tools and some expertise. Not sure if this is an option here.
I ignored them since they would generate a small error in my target text :-)
These warnings should not result in the problem you are facing at the moment. Not sure about the tag order thing. If you had overlapping tags like <a>text<b>text</a>text</b>text, not sure what that would do with your target file. But I don't think this is what we are looking for.
These warnings should not result in the problem you are facing at the moment. Not sure about the tag order thing. If you had overlapping tags like <a>text<b>text</a>text</b>text, not sure what that would do with your target file. But I don't think this is what we are looking for.
The one thing you can try is to convert the source file to some other format like RTF, translate that (you have the translations in your TMs already), then create the target RTF, then convert that to DOCX. Or use the OpenOffice file format.
Yes I was going to ask you this, OK I will try with RFT (or a regular Word file), and will keep you posted! Thank you guys
I'm very time-strapped, but Jerzy Czopik offered to look at your file – that's a golden chance…
I sent it to you and I am currently testing the procedure proposed by Jerzy, as the other simpler workaround (simply using another file type) didn't work
Thank you. Source file can be translated with DeepL and generates a proper Word file, opening with no problems. Please check my e-mail. I hope we'll be able to solve your problem in the proposed way. Do not get me wrong, but I'm certainly faster in doing that 
_________________________________________________________
When asking for help here, please be as accurate as possible. Please always remember to give the exact version of product used and all possible error messages received. The better you describe your problem, the better help you will get.
Want to learn more about Trados Studio? Visit the Community Hub. Have a good idea to make Trados Studio better? Publish it here.
From what you say I conclude that there is a corrupt TU in the TM that inserted the 0x02 character?
Translate
