LO writer supports a fine resolution for controlling paragraph breaking across pages:
1. Can break across pages Yes/No
If Yes, then:
2. No more than [ N ] orphan lines
3. No more than [ M ] widow lines
The same resolution of control should be offered for tables. Right now we only have (1.), but we should have:
Can break across pages Yes/No
If Yes, then:
No more than [ N ] orphan table rows
No more than [ M ] widow table rows
and a choice of whether heading rows count towards that number or not.
I see the use case and would support this. But I don't think we should use the linguistic term "orphan" and "widow", but just use something like
Minimum of [ N ] table rows above break
Minimum of [ M ] table rows below break
cc: Design-Team for further input and decision
(In reply to Dieter from comment #1)
> But I don't think we should use the linguistic term "orphan" and "widow"
I would say that is orthogonal to this bug. I'm just saying we should have the same control for tables that we have for paragraphs. Suggest you open a bug about the terminology (which is just as relevant for paragraphs) and perhaps link it to this one.
So perhaps I don't understand your idea. Sorry.
I wonder if we can realize this with ODF. The attribute of n needs to be stored and made available for all application.
It would be also useful to research if this can be expressed with OOXML.
From a UX POV the fine-tuning of table splitting would be a nice-to-have.