Description: Image moves to different page after DOCX export Steps to Reproduce: 1. Open the attached file 2. Save as DOCX 3. File reload Actual Results: Image from page 1 to page 2 Expected Results: Page 1? Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 3ed9bba283a6a67864c0928186e277240be0d9ba CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
Created attachment 169539 [details] Example file
Created attachment 169540 [details] Reduced example with less noise
@Justin Is this one of those rounding issues? Where image size gets bigger because of measuring difference between DOCX and ODT. Or something else? And if it's rounding, maybe not rounding up?
I confirm it with Version: 7.1.0.3 (x64) / LibreOffice Community Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c 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 What is happening is, that anchor changes from "To Pargraph" to "To Character". Telesto, would be very kind and useful, if you could spend some more time on investigation about what is happening.
(In reply to Dieter from comment #4) > I confirm it with > > Version: 7.1.0.3 (x64) / LibreOffice Community > Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c > 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 > > What is happening is, that anchor changes from "To Pargraph" to "To > Character". Telesto, would be very kind and useful, if you could spend some > more time on investigation about what is happening. Didn't notice that (or didn't look carefully). Conversion to DOCX always including conversion of 'to paragraph' to 'to character' for compatibility reasons
(In reply to Telesto from comment #5) > Conversion to DOCX always > including conversion of 'to paragraph' to 'to character' for > compatibility reasons So what does it mean then: WONTFIX or Enhancement or something else?
@NISZ/ @Miklos Any idea about this. DOCX converts 'to paragraph' anchors to 'to character' which causes a layout change in the specific consternation here. A manual change of the anchor does - obviously - the same thing The question is: So what does it mean then: WONTFIX or Enhancement or something else?
docx only has to-char (anchored) and as-char (inline), so if the request is to preserve to-para in docx, that's a wontfix.
(In reply to Miklos Vajna from comment #8) > docx only has to-char (anchored) and as-char (inline), so if the request is > to preserve to-para in docx, that's a wontfix. I don't care much about anchoring type. I assume the 'conversion' from 'to paragraph' 'to character' is done with the idea in mind that the page should look the same. It mostly works as expected. However the current example shows a case where 'to paragraph' looking different from 'to character' anchoring. This because the anchor - to character - attaches itself to the paragraph below. However anchors are kind of 'hairy'
To be kind of more specific.. bulleted list is involved.
It seems like the image is anchored to the beginning of the bulleted "Low Color Reference" paragraph and has a <text:soft-page-break/> in the odt, which is not exported to docx, but other properties seem to be exported fine. I'm not sure whether there is anything in docx that could be used here.
*** This bug has been marked as a duplicate of bug 94302 ***
*** This bug has been marked as a duplicate of bug 135581 ***
Michael Stahl committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/dd3c70518851b532f43a853d8e0c6189013844c4 sw: fix assert on tdf140219-2.odt It will be available in 7.6.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.