• State Suggested Answer
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 433 subscribers
  • Views 4341 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
  • 0
    Hi ,

    You didn't tell us what version of Studio you are using, but I do know that I have seen this with the new Word filetype in Studio 2015 and 2017 where the user is working with an older version of Microsoft Word. In these cases I was able to open the file without a problem in Word 2016.

    The solution in these cases was one of these:

    1. Don't worry about it as the client had a more recent version of Word and had no problem with the file
    2. Upgrade the version of Word to something more recent
    3. Try processing the file again by working on the DOCX and not the PDF.

    To do the last one the process would be this:

    1. Open the PDF in Studio using the single file approach (Ctrl+Shift+O)
    2. Immediately close it and you'll find a DOCX with the source content in the same folder as the PDF
    3. Clean up the DOCX - TransTools is a good approach - appstore.sdl.com/.../
    4. Translate the cleaned up DOCX instead

    Regards

    Paul

    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

  • 0 in reply to Paul
    Hi Paul,

    Sorry, forgot to mention, I am using SDL Trados 2017. The thing is with your solutions is that I am using Microsoft Office 2016, so those first two solutions aren't applicable unfortunately. I really don't want to retranslate the entire document as I've already finished it and it's pretty long. Do you have anything else I could try?

    Thanks for your answer,
    Rosie
  • 0 in reply to Rosie Marsland
    Hi ,

    The retranslate shouldn’t take too long as it’s mostly automatic from your Translation Memory. There may be some changes because of tag differences here and there but if you set the Pre translate setting when you run the Pre-translate batch task to less than 100% then that should help pick all the translations up.

    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

  • 0 in reply to Paul
    Hi Paul,

    We've been having the same problem more and more now at our company. The problem occurs for us when an ampersand is present in the project's file path: In the Word file's XML code, the ampersand is encoded as "&" instead of "&" which generates an XML parsing error when you try to open the Word file ("We're sorry. We can't open xyz.docx because we found a problem with its contents. Details: Xml parsing error")

    We've been able to fix it each time by opening the Word file's archive and editing the document.xml file (changing "&" to "&"). (I saw that Luke Hipsher suggested a similar solution on this thread in 2016: community.sdl.com/.../9137

    This solution is however tedious and time consuming and the file has to be sent to engineering each time.

    Any idea what the source of the problem might be?

    Thanks in advance,

    Madeleine
  • 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 works. 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.
  • 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.