Inserting manual break corrupted docx file save

[VRad]

I’ve been using LO for a month without issue. Unfortunately after discovering docx ‘compatibility’ I’ve been saving and retrieving to/ from docx format - not realizing the term compatibility means different things to different coders. Lesson learned.

My today problem is the LO → docx file save was corrupt as was my manual backup which was taken after the corrupt save.

The error message references an XML error at line two - like many other help requests online.

The single workflow difference between successful saves over a month and yesterday’s corruption was the format change from the document default portrait to landscape for a single mid-document page.

Per help threads I have tried without success to 1) open files in a licensed copy of Word and 2) open files in File Viewer Plus.

Using Notepad I have confirmed that the file contains actual content and is hopefully recoverable.

Any help would be appreciated!

Thanks… VR

[VRad]

@fpy I appreciate the offer but the contents were sensitive.

Solution: I pulled the docment.xml out of the archive and converted it to a text file. With that I manually stripped out the xml and I’m ready to start formatting it.

Thank you everyone for the help!!

…VR

[EarnestAl]

Save as .odt and if you need to send somebody a copy in .docx, then click file > Save a copy and send that copy. It avoids multiple conversions (every time you open or save a .docx it gets converted) which can bring the risk or corruption.

[VRad]

Thanks @EarnestAl. Good advice!

[fpy]

@VRad

the file

a possible fix :

I repaired a dreaded "Format error in content.xml" in ODS file on Macintosh

Yes, and for that use an XML tool like xmllint to process and format the extracted from the zip content.xml and freshen the zip archive and reload the document in LibreOffice, so it can tell a better position instead of 2,2209664(row,col). e.g. unzip document.ods content.xml xmllint --format content.xml >new.xml mv new.xml content.xml zip -f document.ods content.xml It could had been helpful if you made the exact content of that portion available so someone could take a look what exactly wen…

[VRad]

@fpy: Thanks for the link. Editing the XML from a command line is beyond me.

@koyotak: I’m not sure what the ‘crutch’ reference is, but I appreciate the help.

Update: Exact error msg:

SAXParseException: '[word/document.xml line 2]: Opening and ending tag mismatch: sdtContent line 2 and txbxContent
', Stream ‘word/document.xml’, Line 2, Column 2584(row,col).

I've looked into the LO docx file, isolated the Column 2584 reference to the following </wps:txbx>

Does anyone know what matching tags look like on this?

Thanks again... VR

[fpy]

@VRad

beyond

depending on privacy concerns, you may upload or PM your file, like in the numerous previous cases … Search results for 'SAXParseException' - Ask LibreOffice

[koyotak]

Die Krücke als Parallel-Datei: Der Export als Hybrid-PDF implementiert die rekursive LibreOffice-Datei und macht jene auf der Windows-Plattform zumindestens lesbar. Jede LibreOffice-Datei ist jedoch in der Windows-Office-Suite selten lesbar, editierbar, was Frust erzeugt auf beiden Seiten. Win-Office ist firmenweit der Standard, LibreOffice jedoch nicht.

---

The crutch as a parallel file: Exporting as a hybrid PDF implements the recursive LibreOffice file and makes it at least readable on the Windows platform. However, every LibreOffice file is rarely readable or editable in the Windows Office suite, which creates frustration on both sides. Windows Office is the company-wide standard, but LibreOffice is not.