openoffice-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From birgitte nielsen <birgitteelmerniel...@hotmail.com>
Subject RE: OpenOffice 4.0 cannot open .doc file LO 4.1 can
Date Sat, 14 Sep 2013 07:22:50 GMT
I think that this mail is sent to the wrong.
 
> Date: Fri, 13 Sep 2013 22:39:23 +0200
> From: db@tasit.net
> To: users@openoffice.apache.org
> Subject: Re: OpenOffice 4.0 cannot open .doc file LO 4.1 can
> 
> R N D Martin wrote:
> > In article <52334694.5060807@scootersdesk.com>, scooter@scootersdesk.com (Scooter)
> > wrote:
> >
> >> *From:* Scooter <scooter@scootersdesk.com>
> >> *To:* users@openoffice.apache.org
> >> *Date:* Fri, 13 Sep 2013 13:08:36 -0400
> >>
> >> Win 7 AOO4.0
> >> I did as suggested: changed the doc to docx and it opened without 
> >> further problems.
> >> I agree with Dave this should not have occurred and I hope it will 
> >> be addressed in the next upgrade.
> >> I will apply this "trick" on other problem doc files.
> >>
> >> Take Care.
> >> Scooter
> >> College Park, MD USA
> >>
> >> Dave Barton wrote on 9/11/2013 2:14 AM:
> >>> TN Patriot wrote:
> >>>> On Tue, 10 Sep 2013 20:06:18 -0700
> >>>> NoOp <glgxg@sbcglobal.net> wrote:
> >>>>
> >>>>> The MS Doc file on:
> >>>>> https://www.socialsecurity.gov/ssi/text-understanding-ssi.htm
> >>>>>
> >>>>>   USSI (MSWord)
> >>>>>   (311 KB doc)
> >>>>>
> >>>>>
> >> <https://www.socialsecurity.gov/ssi/documents/USSI%202012%20%20final
> >> %20clean%20copy%20on%203-30-12.doc>
> >>>>> Cannot be opened with AOO 4.0. However it opens without issue 
> >> using
> >>>>> LibreOffice 4.1.
> >>>>>
> >>>>> AOO:
> >>>>> AOO400m3(Build:9702)  -  Rev. 1503704
> >>>>> 2013-07-16 14:49:37 (Tue, 16 Jul 2013) - Linux x86_64
> >>>>>
> >>>>> LO:
> >>>>> Version: 4.1.0.4
> >>>>> Build ID: 89ea49ddacd9aa532507cbf852f2bb22b1ace28
> >>>>>
> >>>>> The error message is:
> >>>>>
> >>>>> "The file 'USSI 2012 final clean copy on 3-30-12.doc' is 
> >> corrupt and
> >>>>> therefore cannot be opened. OpenOffice cna try to repair the 
> >> file.
> >>>>> The corruption could be the result of document manipulation or 
> >> of
> >>>>> structural document damage due to data transmission.
> >>>>>
> >>>>> We recommend that you do not trust the content of the repaired 
> >> document.
> >>>>> Execution of macros is disabled for this document.
> >>>>>
> >>>>> Should OpenOffice repair the file?"
> >>>>>
> >>>>> Clicking 'Yes' results in "Read-Error. Error reading file."
> >>>>>
> >>>>> And anyone reproduce?
> >>>>>
> >>>> Does the same here with my 4.0 also, but I don't believe it's a 
> >> correct 'doc' file.
> >>>> It's put together more like a archive. Maybe LO is set up to 
> >> open archives for some
> >>>> reason?
> >>>>
> >>>>
> >>> It is in archive not binary (.doc) format. Change the extension 
> >>> to .docx
> >>> and it opens fine in 4.0 This suggests that AOO is only relying 
> >>> on the
> >>> file extension to determine which filter to use instead of 
> >>> analysing the
> >>> file header. I propose a bug report (RFE?) to fix this, plus a bug
> >>> report to fix the infinite loop if the user answers "No" in the 
> >>> "Repair"
> >>> dialog.
> >>>
> >>> Dave
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >> --------------------------------------------------------------------
> >> -
> >> I've had no problems with docx files with this and earlier versions of AOO for
some
> >> time now.
> >>
> >> Niall Martin
> 
> That's good news, but change the file extension of a file from ".docx"
> to ".doc" then try to open in AOO and you will understand what this
> thread is about. If you are interested how/why this file extension
> change can/does happen read the comments in the 2 bug reports I linked
> to in another post to this thread.
> 
> Dave
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: users-help@openoffice.apache.org
> 
 		 	   		  
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message