Bug 99025 - [FORMATTING, FILESAVE] Table's Column break-After is not properly exported as .doc/.docx
Summary: [FORMATTING, FILESAVE] Table's Column break-After is not properly exported as...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:doc, filter:docx
Depends on:
Blocks: DOC
  Show dependency tree / graph
 
Reported: 2016-04-01 13:46 UTC by Nicolas Mailhot
Modified: 2023-04-15 03:27 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Testcase (85.59 KB, application/vnd.oasis.opendocument.text)
2016-04-01 13:46 UTC, Nicolas Mailhot 		Details
99025_tableColumnBreakAfter.odt: simple, but different outcome, test document. (11.75 KB, application/vnd.oasis.opendocument.text)
2021-04-12 17:14 UTC, Justin L 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Mailhot 2016-04-01 13:46:18 UTC 
Created attachment 124012 [details]
Testcase

In the attached testcase, when saving as .doc and opening in word 2007, the column breaks in chapter 2.1.2, 2.1.3, etc are not properly exported
Comment 1 Buovjaga 2016-04-14 12:36:00 UTC 
Reproduced.

Win 8.1 32-bit
MSO 2013
LibO Version: 5.2.0.0.alpha0+
Build ID: 92d7fef02574051826e46a3a7e3d33a1afa062d7
CPU Threads: 4; OS Version: Windows 6.29; UI Render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2016-04-14_03:18:53
Locale: fi-FI (fi_FI)
Comment 2 QA Administrators 2018-06-15 02:46:23 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2020-06-15 03:40:27 UTC Comment hidden (obsolete, spam)
Comment 4 Justin L 2021-04-12 17:14:00 UTC 
Created attachment 171133 [details]
99025_tableColumnBreakAfter.odt: simple, but different outcome, test document.

I'm not sure if this document mimics OP's problem closely enough(it doesn't seem to since it doesn't introduce a continuous sectionbreak), but it does show that the column break on the table is simply not even seen on export of doc, and DOCX also doesn't work properly.

In OP's example, the tables themselves are set with Column-BreakAfter - which Word can't handle directly, so it has to be moved to the following paragraph as a column-BreakBefore. But for some reason it is exporting as continuous section break instead of a manual break (at least, according to Word 2003) - also for DOCX.

P.S. Always using BreakBefore exports nicely.
Comment 5 Justin L 2021-04-14 10:46:52 UTC 
This one would be really complicated to solve. Somehow, you have to keep track of the fact that the table-start indicates a column-break-after. Then many (cell) paragraphs can go by, and even table-in-table-ends. Then, on the following paragraph (or table), a column-break-before would have to be issued.

At the moment, the column break is never even seem during the DOC export, and it is ignored in DOCX since it isn't a bBefore in an m_bBreakBefore zone.

Since DOC and DOCX share the same export code but work very differently, I'm not even going to attempt to handle this situation. This is a regression disaster waiting to happen.
Comment 6 QA Administrators 2023-04-15 03:27:15 UTC Comment hidden (spam)