Apache OpenOffice (AOO) Bugzilla – Issue 8409
Unable to open MS Word 2000 docs
Last modified: 2003-09-08 16:56:16 UTC
I'm having problems opening various different docs created with my installation of Microsoft Word 2000 (9.0.3821 SR-1). An example file will be attached. When I try to open this file, *nothing* happens. If I pass it on the command line, OOo will display splash screen, appear to be working for a while, then exit. No error messages are given, and main window never appears. If I use File->Open... instead, the file selector is closed and nothing more happens after the file is selected. (But OOo doesn't crash or anything.) I get the same behaviour when saving as Word 6.0/95, but RTF work fine.
Created attachment 3196 [details] MS Word file that fails to open in OOo
A word 2000 document that we are rejecting as not being openable!.
This doc has a different clipboard id that every other word 2000 doc, very strange indeed. Anything unusual about your copy of word ? or your platform ?. I can fix it and it will work in the next SRX644, but can you attach a word 6/95 document that also fails to confirm that my fix will work for those as well.
I should have mentioned this: This particular document was created on an emulated setup (WINE/CrossOver Office.) I thought I'd seen it with documents from a setup installed on real Win 2000 off the same CD, too, though but perhaps not. I'm absolutely sure that the Win installation never complains about the documents created this way, though. Anyhow a fix would be really useful. Giving some kind of feedback if when when the conversion fails is however even more important.
Created attachment 3214 [details] The same doc saved as Word 6.0/95
Interesting, wine might have a bug with their structured storage implementation of some kind. .doc's have a \1CompObj stream which is different in a normal win2000 created doc than that example. CompObj under win2000 for me is... 01 00 FE FF 03 0A 00 00 FF FF FF FF 06 09 02 00 00 00 00 00 C0 00 00 00 00 00 00 46 18 00 00 00 4D 69 63 72 6F 73 6F 66 74 20 57 6F 72 64 20 44 6F 63 75 6D 65 6E 74 00 0A 00 00 00 4D 53 57 6F 72 64 44 6F 63 00 10 00 00 00 57 6F 72 64 2E 44 6F 63 75 6D 65 6E 74 2E 38 00 F4 39 B2 71 00 00 00 00 00 00 00 00 00 00 00 00 The wine one is... 01 00 FE FF 03 0A 00 00 FF FF FF FF 06 09 02 00 00 00 00 00 C0 00 00 00 00 00 00 46 18 00 00 00 4D 69 63 72 6F 73 6F 66 74 20 57 6F 72 64 20 44 6F 63 75 6D 65 6E 74 00 FF FF FF FF 3D 02 00 00 10 00 00 00 57 6F 72 64 2E 44 6F 63 75 6D 65 6E 74 2E 38 00 F4 39 B2 71 00 00 00 00 00 00 00 00 00 00 00 00 After the second FF FF FF FF in this second example is the clipboard id of the document, here its 3d 02 00 00 i.e. 0x23d while we expected to either see 0x3f for a winword clipboard id or nothing at all as in the word2000 under win2000 created documents. It might not be a wine bug, just something triggered by the different environment.
Working in SRX644h
I have seen similar behavior with Word 97-created documents. Again, the Word-97 is running on CrossOffice Wine. (e.g., File|Open fails silently) 1. I copied the documents over to Windows 2000, and the same version of Word 97. File|Open works, and can save the file back out. 2. Obviously, 'diff' reports that the aberrant files are different, after being saved by Win2K/Word97 combination. 3. Copying those 'newer' file back to Linux, Open Office is happy to load the file. Thoughts: If Wine indeed causes the file to be saved differently than the Win2K environment, the file is still considered to be legit by Word97. How many variations are considered acceptable, I don't know. Nonetheless, whether you modify OO to deal with the different format or not (I'm leaning both ways: Wine should be repaired if that's the issue; Windows XP++ may present another variation, so you should be open to making the fix(es) now), I advise an error dialog rather than silent failure.
*** Issue 8247 has been marked as a duplicate of this issue. ***
*** Issue 8071 has been marked as a duplicate of this issue. ***
Just so you know: According to CodeWeavers, this is a known issue with WINE, and there will be a fix in the next release. I think being able to read this documents in OOo would still be useful, though. And there definitely ought to be a dialogue box for failed import - if at all possible, describing in some detail why the conversion wasn't successful.
Just for my own interest, is there a wine bugtracking system and id for this issue? I'm always interested in ole2 file format details.
WINE Bugzilla is located at http://bugs.winehq.com/. I didn't find this issue there, though, but I didn't look very hard. My request to CodeWeavers support is tracked at http://support.codeweavers.com/viewticket.php?ticket_id=18570
Created attachment 3500 [details] The same file saved with CrossOver Office 1.3.1
Everything looks a lot better when the new CrossOver Office 1.3.1 is used. Its internal wine version is 20020710. I've attached a version of my test-file that was re-saved using the same MS Office installation with the new CrossOver/WINE; it opens just fine in OOo 1.0.1.
Tested with 644L. Such files as posted will be also accepted by OpenOffice 644.
*** Issue 9376 has been marked as a duplicate of this issue. ***
Fix will be included in OpenOffice 1.1 beta.
*** Issue 12093 has been marked as a duplicate of this issue. ***
I have this exact same problem except my word documents were not created in Wine, they were created in W2k on Office XP. I will attach the document.
Created attachment 5939 [details] problem document