https://bugs.documentfoundation.org/show_bug.cgi?id=126677
Justin L <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also|https://bugs.documentfounda |https://bugs.documentfounda |tion.org/show_bug.cgi?id=13 |tion.org/show_bug.cgi?id=15 |4257 |3964 --- Comment #16 from Justin L <[email protected]> --- Bug 153964 documents the logic of what is happening here, at least for non-section page and column breaks for DOCX. In MS formats, we have a paragraph with a break in it somewhere <w:p> ... some possible runs of text (or shape anchors etc.) w:br type="page" or "column" ... some more possible runs of text </w:p> In LO we have the break as a paragraph property, but in Word it is more of a character property. In LO we have two paragraphs, but in Word it is only one paragraph. And that explains why paragraph top margin, top border, first line indent etc don't apply on the "new page" - because they were already applied to the start of the paragraph on the previous page or column before the break. In older versions of MS Word, that logic wasn't always consistently applied - especially if w:br was the first "run" in the paragraph. Personally, I think it makes sense for a normal paragraph to not have any spacing above when it naturally starts on a new page. The whole point of having spacing is to separate it from other content, and at the top of a page or column it certainly is separated from the previous content. Otherwise it is a waste of space. To make it more export compatible with MS Word, we would need to specify that "top margin" would need to be ignored for normal breaks, and only applied for "with page style" breaks(aka section break). However, I personally like the current consistent ODT logic that any "forced page start" must not ignore top margin for the first paragraph. I would not advise a change for that (unless it is added to a make-LO-work-like-mso compatibility flag). -- You are receiving this mail because: You are the assignee for the bug.
