Created attachment 139150 [details] sample spreadsheet file The attached file is correctly displayed in Libre Office (in versions 5.1.6 and 5.4). But when exporting it in HTML (or when clicking in "Preview in browser") the images "Browser" and "Browser details" (i.e. the rightmost objects in the file) are displayed *at the bottom* of the HTML file. Could this be eventually fixed by a certain configuration parameter?
Exporting in PDF exhibits the same bad image positioning.
Hi I tested the xlsx file and the both images are down the HTML file But when saving the xlsx file in a ods file then with LO 5.4.4.2 and 6.1.0.0master both images are on the place where they belong My suggestion is save the file in the native ods file from LO and then export to HTML file
>My suggestion is save the file in the native ods file from LO and then export to HTML I've tried that (with LO 5.4) and got the same result! How did you get a good HTML representation? Me I have tried in 2 ways (after loading the ODS file): 1) File -> Export -> XHTML : the browser's console exhibits some errors, but no image is displayed; however in the document there are some <img style="height:14,879cm;width:20,249cm;" alt="" src="data:image/*;base64,VkNMTVRGAQAx...> tags 2) File -> Save as -> HTML Document (Calc) -> here I get an HTML file + some png images, but the 2 at rightmost are actually displayed at the bottom. I shall try with the 6 version to see what happens.
Created attachment 139183 [details] XLSX file transformd in ODS
Created attachment 139192 [details] saved to html with different LO versions Here you have all test i have done with attachment 139150 [details] that i saved as a ods file
With File => export=> xhtml i have the same results like you explain in comment 3, i have also the wrong results, no images at all, only text But with File => save as => html document then i have the correct results, see the zip file; i did forgot to explain properly Best regards
Created attachment 139210 [details] Conversion results The original XLSX file, converted to ODS using LibreOffice 5.1.6.2 and then converted to HTML.
Yes! Your ODS file, displayed with my LibreOffice 5.1.6.2 (from Ubuntu Xenial) is correctly converted to HTML! There's actually no need to convert it to HTML, one should simply select "Preview in web browser". However, my ODS file, generated with the same LibreOffice 5.1.6.2 **is different** and produces the result you see in the attached ZIP ("Conversion results"). So either the results depends on the LibreOffice version (which one did you use to convert the file?) or on the user parameters - that's why I have enclosed in the ZIP my ~/.config/libreoffice/4/user folder.
Basically all is related to the conversion to the ODS format -> your conversion is more suitable to be displayed as a HTML file, mine not! :-(
@Marian first download a AppImage from https://libreoffice.soluzioniopen.com/ 5.4.4.2 or 6.0.1.0; you only need make them executable second in the ods file you need to move a bit the OS an browser image; a bit lower and between them a bit more space this will give you the same results as i have become when tested Best regards
Will close because as its working for me in "preview in browser"; "save as HTML document" If you or not agree, you can still reopen the report Best regards
According to the answer I've got >in the ods file you need to move a bit the OS an browser image; >a bit lower and between them a bit more space For me there are 2 problems/bugs actually: - the internal representation of an XLSX file could not be automatically converted to an identical HTML representation, one should apparently pass through an intermediate stage of converting the image to the ODS format, - even in this case the result needs to be manually trimmed in order to get an acceptable HTML representation, albeit the fact that LO displays it well.
There's actually no need to pass through an ODS file - even the original XLSX file, once the images rearranged by hand, is saved correctly in HTML format. However this prevents any possibility to do script conversions (using '--headless--nofirststartwizard --nolockcheck --nologo --invisible' options) with LibreOffice...
You can't confirm your own bugs. Moving it back to UNCONFIRMED until someone else confirms it.
Well, it seems that Xavier Van Wijmeersch reproduced my problem, except that his solution is unacceptable for somebody who tries to perform batch conversions with Libre Office...
Any news about this bug?
Tests done with LO 5.1 (from Ubuntu 16.04) and 6.0.
** Please read this message in its entirety before responding ** 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 can confirm that the bug is present in Version: 6.2.2.2 Build ID: 6.2.2-4 CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: gtk3; Locale: it-IT (en_GB.UTF-8); UI-Language: en-GB Calc: threaded
Dear Marian, 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
Dear Marian, 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