Created attachment 135834 [details] Example files, see description If you use an image for background filling, e.g. a page background, then the image is specified by the <draw:fill-image> element in <office:styles> in styles.xml in the package. This element references the image itself in the Pictures folder in the package. If you use the flat ODF format, then no folder Pictures exists. LibreOffice writes the <office:binary-data> element as child of <draw:fill-image> to store the image base64 encoded. But that child element is not allowed in ODF 1.2. I have written https://issues.oasis-open.org/browse/OFFICE-3933 to get LibreOffices behavior into ODF 1.3. I think, that there is no need to put something temporarily into loext namespace, because LibreOffice is the only application which can read and write flat ODF. Or do you know another one? If you use a link to an external image in <draw:fill-image>, that is valid ODF 1.2. Such link works in packed format although LibreOffice has no UI to link an external background image. But it fails in flat format. That is, what this issue is about, LibreOffice should be able to interpret links to external images in flat format as well. The attached zip-file contains an image Clipart.png which is linked from ImageBackgroundexternalImage.fodp and from ImageBackgroundeternalImage.odp. The file ImageBackground_strict.fodg is written by LibreOffice and contains the faulty <office:binary-data> element. To validate the flat ODF file against the RELAX NG schema, you can use xmllint on Linux or Cygwin or use the Jave program jing on Windows.
Let's set to NEW. (In reply to Regina Henschel from comment #0) > LibreOffices behavior into ODF 1.3. I think, that there is no need to put > something temporarily into loext namespace, because LibreOffice is the only > application which can read and write flat ODF. Or do you know another one? I found another one: http://fletcherpenney.net/multimarkdown/
The ODF TC has agreed to OFFICE-3933. I do not found where in http://fletcherpenney.net/multimarkdown/ images are used.
Dear Regina Henschel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I suggest to keep this open until ODF 1.3 is released, to make sure, that the needed element is indeed included in the new ODF version.
Dear Regina Henschel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Using base64 is now allowed for ODF 1.3. So I close this bug report. I'll write a new bug report, that the linked background image is not read.