On 07/18/2012 12:16 AM, Doug wrote:
On 07/18/2012 12:38 AM, Duaine Hechler wrote:
On 07/17/2012 08:18 PM, James Knott wrote:
Duaine Hechler wrote:
What will open MS Word 2010 ? LibreOffice ? OpenOffice ? Nothing yet ?
Both of those should open Word documents, both .doc and .docx.
Yes, but those are Word >=2007. Attached is the file in question. Linux sees it as a zip file.
Duaine
1. The file opened without complaint in Symphony, a cousin of OO and LO 2. The file would not open in OO 3.4. It said the file was corrupt, and tried to fix it but could not. 3. The file would not open at first in LO 3.5. It said the file was corrupt, and tried to fix it, with apparent success.
You may make of this what you will. Symphony has some bugs, but it looks more polished than the other two, and to my mind, it is more user friendly, so I use it. It's not in the repo for my distro, so I got the rpm from IBM and installed it that way, and I've been using it ever since, even tho I have the other two on the machine also.
--doug
I ran the same tests with openoffice 3.4 and got similar results. There is a generic bug in the way OO/LO handles docx files with .doc extensions. I filed https://issues.apache.org/ooo/show_bug.cgi?id=120309 with Apache for openoffice. Somebody will need to do the same either here as Lars suggested or upstream with freedesktop. If you want to cut and paste, the contents of my bug report is: -------------- bug report ------------------ When opening a MS docx file with a '.doc' extension AOO 3.4 writer displays a warning that the file is corrupt and cannot be opened and asks to repair the file. (see docx-warning.jpg included in attachment) If you choose 'NO', writer then says that the document could not be repaired and cannot be opened. (see docx-warning2.jpg) (you should also delete 'therefore' from the warning -- it is superfulous) The file PERINNIAL.doc is also included in the attachment. However, instead of closing the file-open dialog and returning to the blank document, writer then immediately displays docx-warning.jpg again, followed by docx-warning2.jpg. It then loops another time with docx-warning.jpg followed by docx-warning2.jpg. At this point, I was considering manually killing the writer process from the command line. But, I kept cycling through the dialogs choosing 'NO" each time when offered to repair, then suddenly, the document just opened in writer. There is a bug in the way writer handles docx files with a .doc extension. writer - Expected Behavior (1) it should be able to determine it is actually a .docx file even though the extension is .doc. It should then handle the .docx file properly (2) if the user chooses 'NO' when prompted to repair, then writer should quit trying to repair the document and simply display the blank 'new document' page. writer does correctly handle the file if the file is renamed from .doc to .docx -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org