https://bugs.documentfoundation.org/show_bug.cgi?id=146264
--- Comment #13 from Svante Schubert <[email protected]> --- I spend this morning looking into this - but I fear there are regressions in the ODF 1.3 part 4 formula spec at this chapter 4.4 some content is missing: https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part4-formula/OpenDocument-v1.3-os-part4-formula.html#__RefHeading__1017896_715980110 I have tested the XSLT "directly" with saxon out-of-the-box using Maven build environment and pom.xml. Otherwise, with LO there would be noise with changing automatic style names during load/save of specs in between tests.My test transformation can be triggered stand-alone via mvn install (activating all test documents in the pom.xml - see https://github.com/svanteschubert/odf-tc/blob/html-floating-fix/pom.xml)All test files and HTML output with indent can be found at my fork: https://github.com/svanteschubert/odf-tc/tree/html-floating-fix/docs/odf1.3/tmp-test-output I can also add some background to the meaning of the XSLT code part - what it does: 1. An ODF paragraph with a draw:frame a child becomes an HTML div not as usually HTML p to be valid HTML. 2. A draw:frame with other elements on the same level (siblings being more than ODF soft page breaks) is becoming a "floating" div (CSS float left) embracing its following siblings within the new div. Until the next following sibling is a draw:frame than this will become a left floating div embracing again its following siblings. This handling is tricky. 3. The variable we are extending "stopAtFirstFrame" is marking a mode to deal with the content before the first draw:frame. The problem that you have correctly fixed - likely partly - earlier, Tor, and I have now understood better is that the above complex CSS floating routine of draw:frame - template mode="frameFloating" - is being triggered from two spots. Aside from <xsl:template match="text:p | draw:page"> the mode="frameFloating" is also entered from draw:frame. Which is why you added the parameter and also from the apply-templates from the list routine, where the duplication is triggered. Sorry, I have to leave this issue now my time-boxed morning is over and I have my own windmills I need to ride against. Please make sure you test the specification before/after for regressions (best after some indent on the XML, e.g. I used manually JEdit editor with the XML plugin), Good hunting, Tor! Svante -- You are receiving this mail because: You are the assignee for the bug.
