Results 1 to 3 of 3

Thread: Libreoffice corrupt file- help please

  1. #1
    Join Date
    May 2021
    Beans
    1

    Lightbulb Libreoffice corrupt file- help please

    hi all, new here. Working on Libreoffice went to open my spreadsheet ( that is 4 months old) and this error message appears: READ ERROR format error discovered in the sub-document content.xml at 2,543247 (row, col)

    after searching online and completing different possible solutions none have worked. Tried the zip- no go. Downloaded a recovery tool- no go. Tried the notepad- do not know what to look for or how to fix ( any suggestions then I can go thru this process)
    This spreadsheet is of great importance and recreating it is not possible after all the time that has been put into it. if anyone has time to respond I would greatly appreciate it. I need help!! Thank you

  2. #2
    Join Date
    Mar 2011
    Location
    U.K.
    Beans
    Hidden!
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: Libreoffice corrupt file- help please

    I have had success in using XMLCopyEditor to open and validate corrupt XML files.

    This last post refers ..

    https://askubuntu.com/questions/4260...th-libreoffice

    I have just looked in Synaptic Package Manager and both packages (including debugger) can be installed from repo.

    I suggest that you first create a backup copy before any such experiments.

  3. #3
    Join Date
    Dec 2014
    Beans
    1,805

    Re: Libreoffice corrupt file- help please

    A few years ago there were two or three cases on this forum of people having corrupted OpenOffice or LibreOffice Writer files with similar error messages. Back then it was a repetition of an attribute, something like
    Code:
    <foo bar="1" bar="2" bar="3>some content of the foo-tag</foo>
    which is clearly not valid, you can't have the same attribute multiple times on one tag.

    Unpack the Office file with zip. Edit the content.xml file with an editor that doesn't get confused by extremely long lines (the content.xml has all content in one unbroken line, potentially several megabytes long) and 'understands' XML and can jump directly to the error (I know emacs can do it in xml-mode and I wouldn't be surprised if vim could too). Pack everything back together. Done.

    Holger

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •