You can usually open xml documents in text-editors such as Notepad,
Gedit, Kate or whatever. Notepad doesn't colour-code it but most
other ones do after you have changed the view from plain text to
something such as html, css or xml or something like that. SciTe is
quite good in Windows. Regina's idea of using a web-browser means
you can't edit the document (i think) but it's a quick and neat way
of getting colour coding without fussing around. Regards from
--- On Wed, 4/1/12, Regina Henschel<firstname.lastname@example.org> wrote:
From: Regina Henschel<email@example.com>
Subject: Re: [libreoffice-users] Error in calc file
Date: Wednesday, 4 January, 2012, 12:34
On 04/01/12 15:58, Jay Lozier wrote:
On 01/03/2012 08:58 PM, Theo wrote:
I have an error in a spreadsheet on opening.
Any help would be very much appreciated.
Format error discovered in the file in sub-document content.xml
Can you open or create a new spreadsheet in Calc? You might have a
corrupted file. However the ods file can be unzipped and you can open
the xml file inside to text editor.
Thanks for the answer Jay.
I have tried some suggestions found by Googling.
1. I copied the file to a new folder and renames it from .sxc to .zip.
2. I extracted the files within.
3. The content.xml file is big - over 4mb. I tried opening it with
and notepad without success.
4. Opened the file in Windows with notepad and got a mass of text -
lines and 1070 columns.
You can open the content.xml file in a browser for example Firefox. It
shows you the place of the error. After you have repaired one place,
open the file again in the browser to show the next error. If the
browser shows a tree view, the file is successfully repaired.
I guess this means I can edit the text, but what do I edit?
As far as I remember there had been two kind of errors.
(1) There are duplicate attributes. You will see exactly same text
before and after the error mark. Delete one of them.
(2) Instead of one _5f or one _20 you see something like _5f_5f_5f.
Reduce them to one.
These errors had been produced be some developer or beta versions long
ago. Your error might be different, but you should look whether it is
one I had described.