https://bugs.documentfoundation.org/show_bug.cgi?id=159166

Mike Kaganski <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|                            |https://ask.libreoffice.org
                   |                            |/t/one-column-title-on-two-
                   |                            |column-page-style/100586

--- Comment #1 from Mike Kaganski <[email protected]> ---
IMO, it would not be correct.
The discussion in
https://ask.libreoffice.org/t/one-column-title-on-two-column-page-style/100586
was about a "single-column header, multi-column chapter". The problem was, that
it is easier to format page style as two-column at once, then apply the
single-column properties (e.g., sections) to headings.

1. From the *logical document structure* point of view, this would be wrong. It
makes headings *nested deeper* (the chapter text is some direct descendant of
the document, while the heading is nested into a section in the document);
while the logical structure is "chapter text is a child of a higher-level
outline object".

2. From the operational point of view, there is an equally easy workaround:
select all text, place into a multi-column section, then put headings into
single-column section. (From the structure PoV, this creates the same "nested
deeper" situation.)

If the proposal of this report would be implemented, it would require that the
page columns be split into separate pieces by the sections. The text would need
to balance itself not to the page column(s), but to some page(s) area between
sections. It looks odd, when the text fills some *part* of the first column,
then (while there is still space in the first column) jumps to a *part* of the
second column; then it jumps back to the first column to insert a section there
(spanning both columns); and then the following text continues on the first
column...

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to