Created attachment 133988 [details] Document contining inline formulae When I have inline formula objects in Writer and export the entire document as XHTML, Writer puts each formula on a separate line when viewed from Firefox. I tried manually changing every occurrence of "block" to "inline", but still got extraneous line breaks. If I export to PDF then I get the corrected results; the formulae are set off with white space but not with line breaks. Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3
You need to set the following <div> elements to inline display too. The problem is not only in the XSLT, but the object itself has already a display="block" attribute in the ODF file format. If you use "Textmode" for the formula, then it is exported without the display attribute, which then defaults to "inline". But the problem with the following div-element remains.
Except specific need, did you try to save this file to html format?
I used export to HTML because I assumed that it would render faster than the PDF that http://mason.gmu.edu/~smetz3 currently uses. Are you suggesting File instead of Export?
(In reply to Shmuel (Seymour J.) Metz from comment #3) > I used export to HTML because I assumed that it would render faster than the > PDF that http://mason.gmu.edu/~smetz3 currently uses. Are you suggesting > File instead of Export? Yep, Save as.
Created attachment 134297 [details] Screen capture of Export drop-down menu Note that the XHTML option exists only for Export, not for Save as.
(In reply to Shmuel (Seymour J.) Metz from comment #5) > Created attachment 134297 [details] > Screen capture of Export drop-down menu > > Note that the XHTML option exists only for Export, not for Save as. I know, but it doesn't matter. Please try Save as HTML.
File -> Save as -> HTML gives me a warning that content may be lost, then puts each formula on a separate line - the same problem as for Export -> XHTML.
Ok, NEW per comment 1.
Whoops! I erroneously opened the XHTML file. The HTML file from File -> Save as -> HTML has a PNG rather than MATHML. Sorry for the blunder.
** 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
The problem does not occur with LibreOffice 6.0.4.2
Hey, that's pretty cool. Let's close.
(In reply to Shmuel (Seymour J.) Metz from comment #11) > The problem does not occur with LibreOffice 6.0.4.2 Sorry, I was testing for a different problem. The formula still appears on a separate line, massively indented, and the text following it does not appear at all.
Created attachment 143361 [details] Exported XHTML with broken inline formula
Created attachment 143362 [details] ODT file for which EXPORT generated bad HTML This reflects test on 6.0.4.2
I can't reproduce it in Versió: 6.0.5.2 ID de la construcció: 1:6.0.5~rc2-0ubuntu0.16.04.1~lo1 Fils de CPU: 4; SO: Linux 4.13; Renderitzador de la IU: per defecte; VCL: gtk3; Configuració local: ca-ES (ca_ES.UTF-8); Calc: group nor in Version: 6.1.0.0.alpha1+ Build ID: 3a801799536e6870f2fb111b1cc00b9575a35a39 CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group nor in Versión: 6.1.0.1 Id. de compilación: 378e26bd4f22a135cef5fa17afd5d4171d8da21a Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; Configuración regional: ca-ES (es_ES); Calc: group threaded Can anyone else reproduce it ?
Repro with attachment 133988 [details] and attachment 143362 [details] Xisco: are you sure you were using Export and not Save as? Save as gives me inline formulas.
I see the error in Version: 6.1.0.0.beta2+ (x64) Build ID: 67a56897ec1e4f2bab2c3291b8dd225710d2ae29 CPU threads: 8; OS: Windows 10.0; UI render: GL; TinderBox: Win-x86_64@62-TDF, Branch:libreoffice-6-1, Time: 2018-06-29_13:19:46 Locale: de-DE (en_US); Calc: CL The formula is on a new line and the text after the formula is missing.
Created attachment 143395 [details] Comparison Libo 4.1 ( left ), Libo 4.4 ( right-top ) and Libo 6.2 ( right-bottom )
Adding bibisectRequest to see when the different changes happened.
Created bug 108491 for the missing text after the formula
(In reply to Xisco Faulí from comment #19) > Created attachment 143395 [details] > Comparison Libo 4.1 ( left ), Libo 4.4 ( right-top ) and Libo 6.2 ( > right-bottom ) The first change is commit 3e33318cd2f00d8aa029904490772c0dcaf715fe Author: Matthew Francis <mjay.francis@gmail.com> Date: Sat Sep 5 18:52:31 2015 +0800 source-hash-1ef63d0842dab4154c5ca2fc42e416950bd7459a commit 1ef63d0842dab4154c5ca2fc42e416950bd7459a Author: Frédéric Wang <fred.wang@free.fr> AuthorDate: Fri Jun 28 17:07:11 2013 +0200 Commit: Bosdonnat Cedric <cedric.bosdonnat@free.fr> CommitDate: Mon Jul 1 13:41:35 2013 +0000 fdo#66278 - MathML export: distinguish inline/display equations.
Dear Shmuel (Seymour J.) Metz, 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
Happy to report that the export looks good to me with: Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: f446a203fa2897bab8ae7686c948a8bf060675c6 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-06-24_15:16:38 Calc: threaded and: Version: 7.2.0.0.beta1 / LibreOffice Community Build ID: c6974f7afec4cd5195617ae48c6ef9aacfe85ddd CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded LO 7.0.6 and 7.1.4 export formulae on separate lines, so I assume the fix happened in the 7.2 branch development.
likely fixed by https://cgit.freedesktop.org/libreoffice/core/commit/?id=06eb655e2c83df8eeeb0c0828f8ac34f13e386af. Closing as dupe of bug 118637. it should be fixed in LibreOffice 7.1.5 *** This bug has been marked as a duplicate of bug 118637 ***