• State Suggested Answer
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 433 subscribers
  • Views 4342 views
  • Users 0 members are here
Options
Related

Parsing error when trying to save MS word file

Rosie Marsland

Hello all,

I have read several other threads on this topic but haven't managed to resolve my error. My Source File was a PDF and I am now trying to save the target translation into MS Word, but when I try to open the Word Target file I have created, it tells me that the file cannot be opened because there is a problem with the contents, "Details:
Xml parsing error.
Location: Part: /word/document.xml, Line: 2, Column: 3155"

I have tried running Verify in SDL Trados to check that all my tags are fine and I didn't come up with any errors in Trados. Other solutions have involved changing the format of the Word source document, but as mine was a PDF that will not help unfortunately. Can anyone please help?

The strange thing is that I could successfully save a target word file earlier in the project. The only thing I can think of is that recently I merged some segments and now it seems to not be saving my Target. However it's hard to know if that did cause the problem, as the successful earlier save occurred some weeks ago, so it may just be a coincidence.

Any help would be much appreciated!

Rosie
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • Former Member
    0 Former Member

    Rosie,
    For this type of problem, there is another quick solution. Just open the Word document using Google docs, which, go figure, just work. Once opened, save it under another name. Problem fixed. Regarding, the other solution, opening the inner document.xml of the Word document (there's a link to this solution in this thread), instead of trying to change something in this xml file, read the text close to the corresponding line and column, then look it up in the Studio editor, delete that segment, or redo it, then generate the target translation. Most likely, it'll work.
Reply
  • Former Member
    0 Former Member

    Rosie,
    For this type of problem, there is another quick solution. Just open the Word document using Google docs, which, go figure, just work. Once opened, save it under another name. Problem fixed. Regarding, the other solution, opening the inner document.xml of the Word document (there's a link to this solution in this thread), instead of trying to change something in this xml file, read the text close to the corresponding line and column, then look it up in the Studio editor, delete that segment, or redo it, then generate the target translation. Most likely, it'll work.
Children
No Data