Apache OpenOffice (AOO) Bugzilla – Issue 2042
Read-Error opening document
Last modified: 2003-09-08 16:56:16 UTC
This might not be the right place to handle this but: I have a document I created in StarOffice 6 (beta) Writer. It is about 10 pages, with many suctom styles, frames, and various formatting techniques. It contains no images. I worked on the file all day, without any problems. I saved it many times. When I save, an app I run continuously makes backups of the file (so I have every save I made). Problem: The file will not re-open. I get a "Read-Error. Unable to open document" every time I try to open it. I've tried about 4 or 5 earlier versions, as well, including the first save, which had little or no formatting at the time. The .sxw file(s) decompress using a zip program just fine, and I can read and edit the files. I've tried recompressing it without the layout- cache, but to no avail. I'm not sure if the problem is with my particular installation or what. I'll attach the document if I can. - Phil DeJarnett
Created attachment 631 [details] This is the last version of the file, which will not re-open
I've done a lot more research, and found it's caused by the style.xml file. I'm not so concerned that I get it fixed, now, but it would be nice to know why the style document was corrupted from the beginning. (It looks fine to me, though).
Reassigned to Eric.
ES->MIB: 3 results after analyse: 1) File is not valid because the child element 'table:table' is not valid as child of a <style:master-page... <style:header. 2) The issue submitted occures because of the <style:header... <table:table... child of the "TOC" master page syle: -> delete it and you can load the document. 3) if I delete all childs and attribute of any <style:header...<table:table... to get this structure: <style:header> <table:table/> </style:header> the document crashes OOo on load. I don't say it makes sense to write such things but the price to pay for this is too high (crash) Tell me if those remarks need to be splitted in different issues.
Note: i can reproduce the crash (3) in the 641n.
XText::setString("") for a header text does not work correctly if the XText contains a table only
Additionaly the API access to headers/footers and text frames that contain a table only or a table at the start or at the end has been fixed. (in 641p)
Closed.