Created attachment 180069 [details] Writer reports `Read Error` on an image file which exists (in the root of the zip dir) #+TITLE: Writer doesn't render an image file which is in the root of zip dir #+CAPTION: *Why does ~Writer~ give a read error, but Google Docs doesn't?* [[./org-mode-unicorn.png]] This image file is at the root of the zip folder, /*instead of in ~Pictures/~*/. 1. ~LibreOffice Writer~ shows me a ~Read Error~ - How the `zip` file looks like :: #+begin_src text M Mode Size Date&time Filename - ---------- ------ -------------------- ---------------- -rw-r--r-- 39 12-May-2022 11:25:32 mimetype -rw-r--r-- 104841 12-May-2022 11:25:32 styles.xml -rwxr-xr-x 10527 12-May-2022 11:25:32 0001.png -rw-r--r-- 207204 12-May-2022 11:25:32 content.xml -rw-r--r-- 647 12-May-2022 11:25:32 meta.xml drwxr-xr-x 0 12-May-2022 11:25:32 META-INF/ -rw-r--r-- 649 12-May-2022 11:25:32 META-INF/manifest.xml - ---------- ------ -------------------- ---------------- 323907 7 files #+end_src - How the ~META-INF/manifest.xml~ looks like :: #+begin_src nxml <?xml version="1.0" encoding="utf-8"?> <manifest:manifest manifest:version="1.2" xmlns:manifest="urn:oasis:names:tc:opendocument:xmlns:manifest:1.0"> <manifest:file-entry manifest:full-path="/" manifest:media-type="application/vnd.oasis.opendocument.text" manifest:version="1.2" /> <manifest:file-entry manifest:full-path="meta.xml" manifest:media-type="text/xml" /> <manifest:file-entry manifest:full-path="styles.xml" manifest:media-type="text/xml" /> <manifest:file-entry manifest:full-path="content.xml" manifest:media-type="text/xml" /> <manifest:file-entry manifest:full-path="0001.png" manifest:media-type="image/png" /> </manifest:manifest> #+end_src - How `content.xml` looks like :: #+begin_src nxml <text:p text:style-name="OrgFigureBody"> <draw:frame draw:style-name="OrgToCharImage" svg:height="4.66cm" svg:width="4.29cm" text:anchor-type="char"> <draw:image xlink:actuate="onLoad" xlink:href="0001.png" xlink:show="embed" xlink:type="simple" /> </draw:frame>Figure <text:bookmark text:name="org2ea9b5d" /> <text:sequence text:name="Figure" style:num-format="1" text:formula="ooow:Figure+1" text:ref-name="org2ea9b5d">1</text:sequence>: Why does <text:span text:style-name="OrgCode">Writer</text:span>give a read error, but Google Docs doesn't?</text:p> #+end_src 2. Google Docs renders the document fine. 3. The ODF Validation[fn:1] on the file succeeds #+begin_src sh java -jar /home/kjambunathan/src/org-mode-ox-odt/testing/examples/odt/odfvalidator-0.10.0-jar-with-dependencies.jar -v imagefileatrootofzipfolder.odt #+end_src [fn:1] See https://repo1.maven.org/maven2/org/odftoolkit/odfvalidator/0.10.0/
Created attachment 180070 [details] Test ODT file: `Read Error` for an image file at the root of zip dir
Created attachment 180071 [details] Google Docs renders the document just fine
(In reply to Jambunathan K from comment #2) > Created attachment 180071 [details] > Google Docs renders the document just fine I uploaded the ODT file to drive and opened it in Google Docs. It renders just fine. https://docs.google.com/document/d/1NQk5qpKL7kBgP8MzeQqnplyNk5ags3gyxCYgvdsUk14/edit?usp=sharing
Version: 7.3.3.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 4; OS: Linux 5.17; UI render: default; VCL: x11 Locale: en-IN (en_IN); UI: en-US Debian package version: 1:7.3.3~rc2-1 Calc: threaded $ dpkg -l | grep writer | grep libreoffice ii libreoffice-writer 1:7.3.3~rc2-1 amd64 office productivity suite -- word processor
I'm not sure, that such structure is valid. Please look at second paragraph in section 3.1 General in https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part2-packages/OpenDocument-v1.3-os-part2-packages.html The image is a document of its own with own mime-type. So it violets the rule of only one document in the root. The validator might be wrong here. Another question is, whether LibreOffice should be error-tolerant and open such files nevertheless. I support such request because Word and TextMaker show the image too.
Dear Jambunathan K, 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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug