odt created by abiword can't be opened by openOffice

This is a bug in libgsf. It also affects gnumeric.

Filed upstream as:

https://bugzilla.gnome.org/show_bug.cgi?id=621043

Martin Sevior

On Wed, Jun 9, 2010 at 9:25 AM, Ophir LOJKINE <email address hidden> wrote:
>
> ** Attachment added: "A file "corrupted" file"
>   http://launchpadlibrarian.net/49979006/L%27ing%C3%A9nu%2C%20chapitre%2020.odt
>
> --
> odt created by abiword can't be opened by openOffice
> https://bugs.launchpad.net/bugs/591503
> You received this bug notification because you are a member of AbiWord
> Stable Builds, which is subscribed to abiword in ubuntu.
>
> Status in “abiword” package in Ubuntu: New
>
> 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.
>
>
>

The upstream bug has been marked as a duplicate, attaching the other upstream bug (seems to be fixed in the upstream repository but not in any release yet).

The bug I reported earlier (#704810), marked as duplicate by Charlie is of a higher importance: dataloss!!!

The only workaround is to only trust and use native .abw or MS .doc converter. MS Office docs created with Abiword are fully compatible with OOo.

In my case only the first page, before the manual page-break, could be saved on opening the abiword-created odt back into abiword after OOo failed to fix any of the corrupted file.

I'm trying to reproduce it with a newly created file to pinpoint if this comes from the way abiword saves the page-break in the odt format or if this comes from other factors (preset numbered headlines, underlining these, combination of several factors).

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.

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.
>
>
>

Please delete previous comment displaying my name and phone numbers.

viktor: We don't have the ability to simply delete or edit comments. I am asking the launchpad team to delete the information. In the meantime, I am marking the bug as private. Only those subscribed will be able to see it.

> Please delete previous comment displaying my name and phone numbers.

It's too late... The log for public bugs is also available on <email address hidden>, which is mirrored by several mail archiving sites (so even if it's removed from Launchpad, there will be tons of copies). Moreover, you've already displayed the same infos in several other bug reports, e.g. #246296, #155501...

Thx for your answers. I will be more careful.
In the meantime I asked question #142647 with the list of comments.

I'm marking this as Fix Released since this was fixed in libgsf 1.14.18 which was shipped in Ubuntu 10.10 and later.

This could be a good candidate for a Stable Release Update for Ubuntu 11.04 if someone would like to prepare it.
https://wiki.ubuntu.com/StableReleaseUpdates

I'm also going to mark this bug as Public again since it looks like the Launchpad administrators have removed the private information.

^ a good candidate for 10.04