https://bugs.documentfoundation.org/show_bug.cgi?id=166544

            Bug ID: 166544
           Summary: FILEOPEN DOC/X: no top spacing after
                    ToC-with-page-break
           Product: LibreOffice
           Version: Inherited From OOo
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Keywords: filter:doc, filter:docx
          Severity: normal
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
            Blocks: 107830, 112682

Created attachment 200754
  --> https://bugs.documentfoundation.org/attachment.cgi?id=200754&action=edit
TopMarginAfterTOC.docx

Normally, after a normal page break, the top paragraph spacing is applied. And
we do that in LO. However, it seems that Microsoft makes an exception to the
case where the page break comes after a Table of Contents field. In that
particular case, no top margin is applied.

Already true in OOo 3.3, so Inherited.

Steps to reproduce:
1.) open TopMarginAfterTOC.docx

On page 2 is the ToC. Notice the big gap between the header and the heading 1
paragraph "Table of Contents" with 48pt of "above spacing". That's all good.

On page 3 is where the problem is seen. In LO we have the same large gap before
the heading 1 paragraph "Chapter 1 48pt", while in MS Office there is no gap at
all.

This oddity was found by looking at overlays from these documents:
abi5309-1.doc
moz1003146-1.doc
novell657806-1.doc
ooo119706-1.doc
ooo23187-1.doc
ooo53044-1.doc

Watch out though for a section page break - that is handled differently...
forum-mso-de-102317.docx and forum-mso-en-13234.docx.

Found by Collabora's mso-test


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107830
[Bug 107830] [META] DOCX (OOXML) paragraph-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112682
[Bug 112682] [META] DOC (binary) paragraph-related issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to