Comment 7 for bug 591503

Revision history for this message
msevior (msevior-gmail) wrote : Re: [Bug 591503] Re: odt created by abiword can't be opened by openOffice

Hi Victor,

Could you email me the offending document? I agree that fixing bugs
like this is of very high importance.

Best Regards,

Martin

On Thu, Jan 20, 2011 at 3:55 AM, viktor <email address hidden> wrote:
> Reproduced: 100% risk of data loss with manual pagebreak after numbered
> headline.
>
> Actually the bug occured on an original OOo-created ODT file. Modified
> by Abiword (Numbered headlines formatting), and saved as ODT, OOo can't
> open it or fix it: formatting error in content.xml 171,39(row,col)
>
> Back into abiword the document is mentioned as corrupted but only part
> of it is still here: DATA LOSS!
>
> See attached file. Note that the original file (created as odt with OO
> writer then opened in Abiword) was 4 pages long. The attachment shows
> the loss seems triggered by a manual pagebreak (already present in the
> original file) following a numbered list (abiword format here).
>
> BUG definitely sounds bigger than what was originally described here.
>
> ** Attachment added: "ODT file created with OO writer, modified then save as ODT (overwrite original) in Abiword, was originally 4pages long"
>   https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/591503/+attachment/1799496/+files/ODTmodif-saveBUG.odt
>
> --
> You received this bug notification because you are a member of AbiWord
> Stable Builds, which is subscribed to abiword in ubuntu.
> https://bugs.launchpad.net/bugs/591503
>
> Title:
>  odt created by abiword can't be opened by openOffice
>
> Status in AbiWord:
>  Fix Released
> Status in “abiword” package in Ubuntu:
>  Confirmed
>
> Bug description:
>  Binary package hint: abiword
>
>  Hi,
>  I use abiword (2.8.2-2ubuntu1.1) to edit my open document files. But when I try to open them back with Open Office writer, it tells me that the files are corrupted, and proposes me to correct the files. If I click OK, it corrects the file, without any problem.
>  The only solution I found to correct the files manually is to unzip and then re-zip the file:
>   (in a new directory)
>  unzip file.odt
>  rm file.odt
>  zip -r file.odt *
>  oowriter file.odt
>
>  I join a file on which the problem occurs.
>
>
>