https://bugs.documentfoundation.org/show_bug.cgi?id=99501
Terrence Enger <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Terrence Enger <[email protected]> --- Created attachment 124727 --> https://bugs.documentfoundation.org/attachment.cgi?id=124727&action=edit .odt with table and paragraph with page-break-before I am setting status NEW and keywords regression, bisected. As Luke's attachment is a .docx, I created the attached dbgutil_20160427.odt. In each version under test, I did... (1) Open dbgutil_20160427.odt from the command line. (2) Save as Microsoft Word 2006-2013 XML (.docx) (3) Close the documemnt. (4) In Start Center, take menu options File > "Recent Documents" and open the just-saved .docx. Working in the 43max bibisect repository, I have reached ... 7c61549622652f6e098fd66456c2d98efeff27fa is the first bad commit commit 7c61549622652f6e098fd66456c2d98efeff27fa Author: Matthew Francis <[email protected]> Date: Thu May 28 19:31:39 2015 +0800 source-hash-a31fbb53dba76736b37213b98b64937f05929a67 commit a31fbb53dba76736b37213b98b64937f05929a67 Author: Pallavi Jadhav <[email protected]> AuthorDate: Thu Feb 6 13:58:03 2014 +0530 Commit: Miklos Vajna <[email protected]> CommitDate: Wed Feb 26 10:50:08 2014 +0100 fdo#74566:DOCX: Preservation <w:br> tag for Break to Next Page Issue : 'Break to Next Page' gets converted to 'Page Break Before' in RT. XML diffrenece : - LO exports <w:br> as <w:pageBreakBefore /> in document.xml - The page break is written into wrong paragraph. Implementation : 1] Removed implementation to export <w:pageBreakBefore />. 2] Added a check to write <w:br> in correct paragraph. 3] Modified code to handle SectionBreak() even if Text node has no string. It is required when DOCX contains a PageBreak with footer. 4] Written Export Unit Test case. Conflicts: sw/qa/extras/ooxmlexport/ooxmlexport.cxx Reviewed on: https://gerrit.libreoffice.org/7891 Change-Id: I237b9c5fdd3083b441f6e81cd8442f458eccf1a0 Bugzilla search shows several possible dups or near misses. I am arbitrarily choosing to confirm this report. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
