You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openoffice.apache.org by bu...@apache.org on 2024/01/10 17:02:54 UTC
[Issue 128437] error reading a LibreOffice file
https://bz.apache.org/ooo/show_bug.cgi?id=128437
damjan@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest|--- |4.2.0-dev
Confirmation in| |
CC| |damjan@apache.org
--- Comment #4 from damjan@apache.org ---
If you unzip the attached Sin.odt and format content.xml nicely (eg. xmllint
--format content.xml), and delete the <draw:a> elements and all their contents,
and zip up the files back into a changed .odt, and open that, then instead of
the error message, it opens successfully and OpenOffice displays empty boxes
where the images should be.
Fiddling further, by deleting some of the <draw:a> elements while leaving
others, we see leaving the 1st and the 2nd but deleting the 3rd shows 2
pictures and 1 empty box, while deleting the 1st and 2nd but leaving the 3rd
still gives the error.
That 3rd <draw:a> element is clearly a problem for OpenOffice. How is it
different from the 1st and 2nd?
The 1st and 2nd elements use this nesting:
<text:p>
<draw:a>
<draw:frame>
<draw:text-box>
<text:p>
<draw:frame>
<draw:image/>
</draw:frame>
</text:p>
</draw:text-box>
</draw:frame>
</draw:a>
</text:p>
The 3rd element uses this nesting:
<text:p>
<draw:a>
<draw:frame>
<draw:text-box>
<text:p>
<draw:a> <======= NEW!!!
<draw:frame>
<draw:image/>
</draw:frame>
</draw:frame>
</text:p>
</draw:text-box>
</draw:frame>
</draw:a>
<draw:a>
<draw:frame>
<draw:text-box>
<text:p>
<draw:a> <======= NEW!!!
<draw:frame>
<draw:image/>
</draw:frame>
</draw:a>
</text:p>
</draw:text-box>
</draw:frame>
</draw:a>
</text:p>
Deleting those inner <draw:a> elements also gets the file to open successfully.
So it looks like OpenOffice's <text:p> doesn't like having a child <draw:a>
element, at least when nested a second time.
However even ODF 1.2 allows having <draw:a> under <text:p>, as is stated in
section 5.1.3 of the specification. So this is not an ODF 1.3 issue, this is a
bug even in our ODF 1.2 implementation.
--
You are receiving this mail because:
You are the assignee for the issue.