<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Word treats section break as column break or page break depending on compatibilityMode" href="https://bugs.documentfoundation.org/show_bug.cgi?id=135343#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - Word treats section break as column break or page break depending on compatibilityMode" href="https://bugs.documentfoundation.org/show_bug.cgi?id=135343">bug 135343</a> from <a class="email" href="mailto:jluth@mail.com" title="Justin L <jluth@mail.com>"> Justin L</a> <pre>It looks like LO NEVER exports a nextColumn section break (nBreakCode = 1). It just uses a normal column break. Hurray! Fortunately, in Word it is not easy to make a column section break. In old Word 2003, it isn't a UI option under "insert breaks". It can only be specified in "page setup", "layout", "section start new column". So, my guess is that LO has absolutely no clue how to handle a real section column break. (Indeed, no unit tests fail if that section of code is just commented out.) What we probably need to do for the compat11 case is to EXTEND the existing section to cover this text (HOW?), and insert a regular column-break-before at the start of the range. (It looks like that is all the columnbreak code is trying to do, except that it fails to extend the previous section. For the compat15 case, it looks like it should just treat a nextColumn as a nextPage. [Need to test the compat version though. What do 14 and 12 do?]</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>