Bug 148975 - TABLE PROPERTIES: Improve table split across pages and columns
Summary: TABLE PROPERTIES: Improve table split across pages and columns
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsDevAdvice
Depends on:
Blocks: Writer-Table-Properties-Dialog
  Show dependency treegraph
 
Reported: 2022-05-07 07:23 UTC by Eyal Rozenberg
Modified: 2022-05-23 07:30 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eyal Rozenberg 2022-05-07 07:23:49 UTC
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.
Comment 1 Dieter 2022-05-21 04:56:18 UTC
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
Comment 2 Eyal Rozenberg 2022-05-21 06:29:42 UTC
(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.
Comment 3 Dieter 2022-05-21 07:05:22 UTC
So perhaps I don't understand your idea. Sorry.
Comment 4 Heiko Tietze 2022-05-23 06:35:36 UTC
I wonder if we can realize this with ODF. The attribute of n needs to be stored and made available for all application.
Comment 5 Miklos Vajna 2022-05-23 07:08:40 UTC
It would be also useful to research if this can be expressed with OOXML.
Comment 6 Heiko Tietze 2022-05-23 07:30:13 UTC
From a UX POV the fine-tuning of table splitting would be a nice-to-have.