Bug 136605 - Export math formula with display="inline" if anchored as character
Summary: Export math formula with display="inline" if anchored as character
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.0.3 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-09 11:57 UTC by Regina Henschel
Modified: 2021-03-25 04:26 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Text document with inline formula (11.37 KB, application/vnd.oasis.opendocument.text)
2020-09-09 11:57 UTC, Regina Henschel
Details
Comparison between html (Firefox) and LO Writer (74.52 KB, image/jpeg)
2021-03-24 08:03 UTC, Dieter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Regina Henschel 2020-09-09 11:57:47 UTC
Created attachment 165315 [details]
Text document with inline formula

Math objects are anchored "as character" by default in Writer. But the generated MathML has the attribute display="block". That means, that the MathML object has to be rendered in a line of its own.

The error becomes visible, if you export the document to XHTML and view it in a browser.

(Export to XHTML has the error, that line content after an object, which is anchored 'as character', is dropped. But that is a different bug.)
Comment 1 Dieter 2021-03-24 08:03:50 UTC
Created attachment 170680 [details]
Comparison between html (Firefox) and LO Writer

Tested with

Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 21c602913d98ef46b49fc9b6f9071db92a1597c6
CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL

But I'm not sure, what I should see there. I can see, that fraction line in html is placed a bit above fraction line in Writer and formula in browser has some more space before "dx".
Comment 2 Regina Henschel 2021-03-24 14:22:23 UTC
(In reply to Dieter from comment #1)
> But I'm not sure, what I should see there.

You see the error, if you do not use 7.2 but 7.1

It is indeed fixed in 7.2, so set to works-for-me.