Created attachment 133876 [details] The File to export Steps To Reproduce: 1. Open the attached ODT File 2. Export the file as XHTML. 3. Open the exported .xhtml file using Firefox. -> the second image is missing -> the text after the first image is missing Browser used: Firefox/53.0
Created attachment 133877 [details] The Result XHTML
Hi mmaurer, I reproduce with LO 5.5.0.0.alpha0+ Build ID: 0e6297932252403883a6057feee488e4ee2bc360 CPU threads: 2; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@39, Branch:master, Time: 2017-05-23_00:14:17 Locale: fr-FR (fr_FR); Calc: CL Could you precise which OS you are using? Thank you, Jacques
OS: Windows 7 Professional, service Pack 1
Observed that saved in html, this file produce a correct file.
The bug can be reproduced in the following version, too: Version: 6.0.0.0.alpha0+ (x64) Build ID: a9588baca8137f51e2ca72e40b1f448b0e1885d1 CPU threads: 8; OS: Windows 6.1; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2017-07-21_04:09:11 Locale: de-DE (de_DE); Calc: CL The created *.html file contains only one image and to little text. I can confirm that the html created by "Preview in Web Browser" and by "Send -> Create HTML Document" is correct.
Created attachment 137708 [details] Modified/Repaired File I figured out that the usage of <text:line-break/> nodes (instead of "normal" line breaks as new paragraph) causes the xhtml export problems. Replacing these nodes in the content.xml with </text:p><text:p> results in a valid odt file which can be exported correctly to xhtml. The attached file contains this fix. An other way to create a exportable odt is to replace the special linebreaks (Shift + Enter) in Writer with normal paragraph switches (Enter).
Created attachment 137810 [details] Path for the xsl transformation from odf to xhtml The attached patch fixes some problems with the xsl transformation from odf to xhtml. multiple <draw:frame> tags divided by <text:s> or <text:line-break> in the same <text:p> tag are now transformed, too: <text:p> <draw:frame> </draw:frame> <text:s/> <--This nodes was lost without path! <text:line-break/> <--This nodes was lost without path! <draw:frame> </draw:frame> <--This nodes was lost without path! </text:p>
** 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
still repro in Version: 6.2.0.0.beta1 Build ID: d1b41307be3f8c19fe6f1938cf056e7ff1eb1d18 CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded
Dear mmaurer, 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
Bug is still present Version: 6.3.3.2 (x64) Build-ID: a64200df03143b798afd1ec74a12ab50359878ed CPU-Threads: 8; BS: Windows 10.0; UI-Render: GL; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: threaded
Happy to report that this is fixed now. In LO 7.2 alpha0+, the second image and all the text show in an XHTML export. The fix must have happened between 7.1 and 7.2. Version: 7.2.0.0.alpha0+ / LibreOffice Community Build ID: 6b09276d157abada74e1a4989700139167207778 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-05-14_04:32:30 Calc: threaded