[opensuse] OpenOffice doc file question
![](https://seccdn.libravatar.org/avatar/7946a5581e1e0b25e548f2b41c69d273.jpg?s=120&d=mm&r=g)
I have a Word .doc file that OpenOffice 3.2 (openSUSE 11.2) will not open. It claims that it is 'corrupt', and offers to repair it. But the repair fails. The .doc file is a zip file containing: Archive: CHEMISTRY B TEST INFORMATION.doc Length Date Time Name -------- ---- ---- ---- 1445 01-01-80 00:00 [Content_Types].xml 590 01-01-80 00:00 _rels/.rels 1449 01-01-80 00:00 word/_rels/document.xml.rels 13818 01-01-80 00:00 word/document.xml 6991 01-01-80 00:00 word/theme/theme1.xml 1669 01-01-80 00:00 word/settings.xml 260 01-01-80 00:00 word/webSettings.xml 15355 01-01-80 00:00 word/styles.xml 635 01-01-80 00:00 docProps/core.xml 3491 01-01-80 00:00 word/numbering.xml 1831 01-01-80 00:00 word/fontTable.xml 1000 01-01-80 00:00 docProps/app.xml -------- ------- 48534 12 files I looked around for a tool (in OpenOffice, I would imagine) that might provide a detail as to why the document is bad. Since I don't know what I am looking for, I may be looking in the wrong place for such a tool. The document is from my daughter's school. I am not sure what version of Word they are using. But I do know that Word can open this document. If I look inside these files, I see in the docProps file this: <Application>Microsoft Office Word</Application> <AppVersion>12.0000</AppVersion> <DocSecurity>0</DocSecurity> Any pointers? -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/f7a1aa12ddf1dca9e24d3931902d0be2.jpg?s=120&d=mm&r=g)
On Wed, Oct 20, 2010 at 10:46, Roger Oberholtzer wrote:
I have a Word .doc file that OpenOffice 3.2 (openSUSE 11.2) will not open. It claims that it is 'corrupt', and offers to repair it. But the repair fails. The .doc file is a zip file containing:
Archive: CHEMISTRY B TEST INFORMATION.doc Length Date Time Name -------- ---- ---- ---- 1445 01-01-80 00:00 [Content_Types].xml 590 01-01-80 00:00 _rels/.rels 1449 01-01-80 00:00 word/_rels/document.xml.rels 13818 01-01-80 00:00 word/document.xml 6991 01-01-80 00:00 word/theme/theme1.xml 1669 01-01-80 00:00 word/settings.xml 260 01-01-80 00:00 word/webSettings.xml 15355 01-01-80 00:00 word/styles.xml 635 01-01-80 00:00 docProps/core.xml 3491 01-01-80 00:00 word/numbering.xml 1831 01-01-80 00:00 word/fontTable.xml 1000 01-01-80 00:00 docProps/app.xml -------- ------- 48534 12 files
I looked around for a tool (in OpenOffice, I would imagine) that might provide a detail as to why the document is bad. Since I don't know what I am looking for, I may be looking in the wrong place for such a tool.
There is no "tool" in OOo that will do something like this.
The document is from my daughter's school. I am not sure what version of Word they are using. But I do know that Word can open this document. If I look inside these files, I see in the docProps file this:
<Application>Microsoft Office Word</Application> <AppVersion>12.0000</AppVersion> <DocSecurity>0</DocSecurity>
This looks suspiciously like a docx file, not a doc file. Is it possible that OOo is trying to convert it from doc binary instead of converting docx? Have you tried renaming to docx, or forcing OOo to open it as docx? I have no idea if it'll work, but worth a try. MS Office 12 is MS Office 2007.... this is the first version of MSO that supported OOXML (ie docx). C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/3ecf74c4da9f2c33803ceccc51ae76a3.jpg?s=120&d=mm&r=g)
Yes, looks like a MS Office 2007 file - essentially a zip I'm also using OO 3.2 on 11.2 and can successfully open .docx files (as well as .xlsx), as well as .doc files that were created using MS Office 2007. In MS Office 2007 , you can set the default saved file format to be .doc, rather than .docx for backwards compatibility with earlier versions of Office. I have had some issues in OO pre-3.2 with large, complex .docx files that failed to initially open. OO would generate a similar message about corrupt files, but would eventually open them. MS Office 2007 Service Pack 2 has native, out of the box support for ODF, ie, no third-party plug-in required. But, users must manually select ODF as the file format when saving or set it as a global default. On 20/10/10 22:03, C wrote:
On Wed, Oct 20, 2010 at 10:46, Roger Oberholtzer wrote:
I have a Word .doc file that OpenOffice 3.2 (openSUSE 11.2) will not open. It claims that it is 'corrupt', and offers to repair it. But the repair fails. The .doc file is a zip file containing:
Archive: CHEMISTRY B TEST INFORMATION.doc Length Date Time Name -------- ---- ---- ---- 1445 01-01-80 00:00 [Content_Types].xml 590 01-01-80 00:00 _rels/.rels 1449 01-01-80 00:00 word/_rels/document.xml.rels 13818 01-01-80 00:00 word/document.xml 6991 01-01-80 00:00 word/theme/theme1.xml 1669 01-01-80 00:00 word/settings.xml 260 01-01-80 00:00 word/webSettings.xml 15355 01-01-80 00:00 word/styles.xml 635 01-01-80 00:00 docProps/core.xml 3491 01-01-80 00:00 word/numbering.xml 1831 01-01-80 00:00 word/fontTable.xml 1000 01-01-80 00:00 docProps/app.xml -------- ------- 48534 12 files
I looked around for a tool (in OpenOffice, I would imagine) that might provide a detail as to why the document is bad. Since I don't know what I am looking for, I may be looking in the wrong place for such a tool.
There is no "tool" in OOo that will do something like this.
The document is from my daughter's school. I am not sure what version of Word they are using. But I do know that Word can open this document. If I look inside these files, I see in the docProps file this:
<Application>Microsoft Office Word</Application> <AppVersion>12.0000</AppVersion> <DocSecurity>0</DocSecurity>
This looks suspiciously like a docx file, not a doc file. Is it possible that OOo is trying to convert it from doc binary instead of converting docx? Have you tried renaming to docx, or forcing OOo to open it as docx? I have no idea if it'll work, but worth a try.
MS Office 12 is MS Office 2007.... this is the first version of MSO that supported OOXML (ie docx).
C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/7946a5581e1e0b25e548f2b41c69d273.jpg?s=120&d=mm&r=g)
On Wed, 2010-10-20 at 11:03 +0200, C wrote:
This looks suspiciously like a docx file, not a doc file. Is it possible that OOo is trying to convert it from doc binary instead of converting docx? Have you tried renaming to docx, or forcing OOo to open it as docx? I have no idea if it'll work, but worth a try.
Hmmm. I was clicking on the document. So OO was deciding what the document was. Renaming the document made the difference. I really would have expected OO to check the contents more than rely on the name. file magic and all that. How odd that the repair of a .doc file does not first look to see if it is in fact a .docx file (a zipped archive rather than a MS Doc format file). I can rename the document. But it makes it necessary to add another step when viewing docs from a browser (as my daughter does via the school's web information system). Anyway, major problem solved. Thanks. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/247f3737bfdd07c80a5411399e9a504c.jpg?s=120&d=mm&r=g)
Roger Oberholtzer wrote:
I can rename the document. But it makes it necessary to add another step when viewing docs from a browser (as my daughter does via the school's web information system).
Wouldn't the mime type tell the browser what to ask oowriter to do? Or is the mime type wrong as well? Or browser action wrongly specified? Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/7946a5581e1e0b25e548f2b41c69d273.jpg?s=120&d=mm&r=g)
On Wed, 2010-10-20 at 11:52 +0100, Dave Howorth wrote:
Roger Oberholtzer wrote:
I can rename the document. But it makes it necessary to add another step when viewing docs from a browser (as my daughter does via the school's web information system).
Wouldn't the mime type tell the browser what to ask oowriter to do?
Or is the mime type wrong as well? Or browser action wrongly specified?
The browser correctly opens OpenOffice for the .doc file. I think it is offered in the dialog you get when you click on these sorts of documents. At lease in firefox. So, I think the browser is fine. It is what OpenOffice does with the badly-named-yet-content-okay document that is the problem. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
C
-
Dave Howorth
-
Roger Oberholtzer
-
Simon Caseley