[Solved] LibreOffice File format error found at SAXParse

[markhand]

Hi,

I'm desperately hoping someone can help. My partner needs to submit the attached in the next 12 hours but on her final save the file has corrupted. We'd be so grateful if someone could take a look and repair. It's a docx file... we have now absorbed the advice from previous posts about saving in odt format.

The error is:
File format error found at
SAXParseException: '[word/document.xml line 2]: Attribute w:eastAsiaTheme redefined
', Stream 'word/document.xml', Line 2, Column 11298(row,col).

Thanks in advance,
Mark

[Hagar Delest]

Hi and welcome to the forum!

I opened the document.xml file with XMLCopy editor and deleted a style just after the VOICE 1 string where the file seemed to be cut.
Then only I could format the file with an XML scheme and it seems to have retrieved the text. I hope you lost the formatting only.

[RoryOF]

Try the attached - check formatting is as desired. I did not have to remove any text, only a duplicate formatting command

[Hagar Delest]

Rory's file is much better than mine!

[RoryOF]

I was able to find the duplicated formatting command and removed it.

[RoryOF]

If markhand's partner is writing another play, note that there is a radio play formatting template at
http://extensions.openoffice.org/en/pro ... g-template

[Hagar Delest]

Strange. I first tried to format the XML file but it couldn't. I then deleted something after the Voice 1 string and it did format the file afterward, without the error about the duplicate formatting. I guessed it was fine. But your finding was better.

[RoryOF]

I opened the archive that is the .docx file, found document.xml (in the internal word folder). I opened this in situ using XML Copy Editor, which reported a format error of duplicate attribute at line 2, 11950. I deleted that attribute, tested for "well formed" in XML C.E., got another duplicate attribute report at the same location, deleted that. This time XML C.E. reported that the file was well formed. I Saved it and was prompted to update it in the .docx archive. The updated .docx archive was what I uploaded.

XML Copy Editor is OK, but its diagnostic messages are not as explicit as they might be. I would welcome a pointer to a more explicit XML analyser that ran on linux, preferably running in a GUI as this is easier for file repairs.

[markhand]

Thank you so much Hagar Delest and RoryOF
I have downloaded both files. Tears of joy have been shed and the deadline shall be met.
If it's not too much trouble, I'd be grateful if you could delete the repaired file attachments from your posts.
We'll check out the radio play template.
Many thanks,
Mark

[RoryOF]

Thank you so much Hagar Delest and RoryOF
I have downloaded both files. Tears of joy have been shed and the deadline shall be met.
If it's not too much trouble, I'd be grateful if you could delete the repaired file attachments from your posts.
We'll check out the radio play template.
Many thanks,
Mark

All deleted, including Hagar's.

[markhand]

Thank you both!

[John_Ha]

XML Copy Editor is OK, but its diagnostic messages are not as explicit as they might be. I would welcome a pointer to a more explicit XML analyser that ran on linux, preferably running in a GUI as this is easier for file repairs.

There seem to be quite a few when I Google for them. You could try an on-line system like Validate an XML file.

When all else fails, deleting all the XML tags is pretty simple and gets back just the text. Use a Regular Expressions Find and Replace with search argument <[^>]+> and replace argument blank. You cannot do it in Writer as it produces a single paragraph which will often be over the 64k limit so I use Notepad++ to do it.

[John_Ha]

we have now absorbed the advice from previous posts about saving in odt format.

That is excellent advice to follow!