Apache OpenOffice (AOO) Bugzilla – Issue 8564
error loading document
Last modified: 2003-03-13 11:13:27 UTC
Sometimes openoffice.org doesn´t let open files and tells me there is a format error in the "parcial.xml file" in the position 2,812 (row, column). Maybe it´s something I´m doing?
dvo->galolaca1: Similar errors (but with 'content.xml' or 'styles.xml') may occur with certain kinds of bugs in the program. But to fix this problem, we need to look at the file in question. So please do this: 1) Try if it works with the latest release (1.0.1). We've fixed several such problems, so maybe yours has already been fixed. You might ask someone else to load the file if you don't have 1.0.1. 2) If that doesn't work, please attach the file that doesn't work to this bug (link: Create a new attachment) Also mention which version (and language) you are using. 3) I am rather intrigued by the "parcial.xml file", since we don't have such a file. Are you sure that's what it said? I would have expected "styles.xml" or "content.xml". What does the word "parcial" mean?
Created attachment 3290 [details] file that cannot be opened
I tried opening the uploaded file in 643c on WinXP and received the following error: Error loading document file:///F:/Documents%20and%20Settings/Brant/Desktop/C--Gabo-nota%20preliminar%20tesis.sxw: Read-Error. Format error discovered in the file in sub-document styles.xml at 2,812(row,col).
Created attachment 3735 [details] fixed document (styles, meta, settings streams deleted)
dvo: The ZIP file is corrupt; the styles.xml, meta.xml, settings.xml streams are broken. Also, the ZIP's central directory structure does not match some of the local ZIP headers (styles.xml). dvo->mav: Please have a lok at this. dvo->galolaca1: I have attached a version of the file without the corrupted streams so you can continue to work. No content was lost, but maybe some formatting needs to be redone. Hope this helps.
mav: There is a 6.1Beta staroffice internal bug that requires a possibility to recover slightly damaged packages. It means that the package component will mark a package as damaged and will try to get as much information as possible. For the mentioned 6.1Beta bug no change in the application level is required. But to recover corruptions like in this issue the application should investigate provided information and probably ignore some corrupted streams or try to recover parsing errors.
Set the target.
To fix crashes should have highest priority => set to P1.
Sorry, I was confused. This is not a crash. But to fix a problem with loading documents is P1, too.
The package reparation is implemented and works with Writer, Calc and Chart documents. The Draw and Math applications should be fixed to transfer the correct error to sfx in case of ZipException. I will create a new bug for them.
StarMath is also fixed.
MAV->TM: Since the bug #106812# is fixed all the applications should be ok.
reopen to send for testing.
MAV->TM: Additionally you can use files from x:\mav\i8564 for testing.
Checked this one in cws cd5 and it looks good ! Set to fixed !
Set to verified !
As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.