Issue 43411

Created attachment 22962 [details]
Data does not show - cursor goes btwn page 2 and 3

Not a p1 anyway. MRU plese have a look.

MRU->ologgio: There are some cells, which do not have the attribute which will
them allow to perform a page break. Select the whole table, go to "Table.Table
Properties" tabpage "Textflow". There, once disable the checkbox "Allow row to
break..." and again enable it. Click OK and the table formatting will look a lot
better now (not perfectly, but I hope this can be also solved in the future).

MRU->FL: I hand this over to you, as long as you are the UserEx contact for the
"Allow table cells to break" spec. 
THe algorithm has been limited to -I think- three levels of "complexity". Means,
when there are too deeply merged cells, the table will be split up though. As
you can see from the attached sample (enable "Allow row..." for whole table
first), there are still documents in the wide world, where this is used (esp.
break from page one onto page two).

MRU: Is the fact that the "Allow row to break..." property not set a problem
with the MSWORD import filter? The document was imported directly from Word. The
original word document is included in the attachment for this issue. Thanks for
your work!

In the Holy Eucharist,
Omar

Made summary a bit more precisely.

*** Issue 72088 has been marked as a duplicate of this issue. ***

*** Issue 72459 has been marked as a duplicate of this issue. ***

*** Issue 74281 has been marked as a duplicate of this issue. ***

*** Issue 84942 has been marked as a duplicate of this issue. ***

add keywords, cc
Follow up Issue 2109

While looking for a solution to my problem with an imported .doc with table, I
found this. It seems to open fine in OO 3.0. If fixed, please note.

Created attachment 58970 [details]
Table does not break in an Imported .doc

Created attachment 58971 [details]
Table does not break in an Imported .doc

While looking for a solution to my problem with a table that does not break in
imported .doc file, I found this "defect.doc". It seemed to me to open fine in
OO 3.0 or I could not find a problem. 

Anyway, I attached my file "table 2-page.doc". Is it the same problem or right
issue? I came here from Issue 84942: "table cells/rows can not continue over a
page boundary". What is interesting is that if I save it in MS Office as .docx,
it opens correctly in OO 3.0.

PS. please delete a duplicate attachment and my previous post.

This problem does *not* only apply to imorted word documents! -inserted .odt-files.
This problem does *not* only apply for complex tables! -one row, two columns.
This problem occurs every day!

The problem can occur on the first page break, but often when a it breaks for
the second time.

The problem does occur on both Linux and Windows.

The problem is *not* solved by "SetOptimalRowHeight" nor with "isSplitAllowed"
or "Split".

I tied to create a macro to 'repair' the document, but it doesn't help in all cases:
---
Sub RebuildAllTables 
	 oDoc = ThisComponent

for i = 0 to oDoc.getTextTables().Count() - 1
   oTab = oDoc.getTextTables().getByIndex(i)
    oTab.Split = FALSE
   for j = 0 to oTab.getRows().Count() - 1
      oRow = oTab.getRows().getByIndex(j)
      oRow.isSplitAllowed = FALSE
      	oProvider = ThisComponent.CurrentController.Frame
  		oDispHelper = createUnoService("com.sun.star.frame.DispatchHelper")
  		oDispHelper.executeDispatch(oProvider, ".uno:SetOptimalRowHeight", "", 0,
Array())
  		oRow.isSplitAllowed = TRUE
   next j
   oTab.Split = TRUE
next i
End Sub
---

Does anyone have any other ideas of how to repair the table?

I think this problem should be fixed soon.

Created attachment 67519 [details]
Problem is on page 2

added my self to CC.

this is really a big bug. if you are building your complex document via uno api
with cascaded tables and now you want to print your document and some cells are
cutted up, this is an absolute no-go. in my case a few rows are not rendered
(during page break). This has to be fixed.

This macro repairs the document/table for me, but it's only a small idea,
because it's just far too slow. Maybe someone has a better solution?


Sub FixTables 
	 oDoc = ThisComponent

for i = 0 to oDoc.getTextTables().Count() - 1
   oTab = oDoc.getTextTables().getByIndex(i)

   if (oTab.Name <> "Master") then
      sNames() = oTab.getCellNames()
      For k = LBound(sNames()) To UBound(sNames())
         oCell = oTab.getCellByName(sNames(k))
         cursor = oCell.createTextCursor()
         vCurs = ThisComponent.getCurrentController().getViewCursor()
         vCurs.gotoRange(cursor, FALSE)
         oCell.insertString(cursor, chr(13), False)
         cursor.goLeft(1, TRUE)
         cursor.setString("")
      next k
   end if
next i
End Sub

Created attachment 71723 [details]
pagebreak in table: Screenshot to locate problem

Created attachment 71724 [details]
pagebreak in table: problem between page 3 and 4

*** Issue 114654 has been marked as a duplicate of this issue. ***