https://bugs.documentfoundation.org/show_bug.cgi?id=159166
ajlittoz <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #2 from ajlittoz <[email protected]> --- (In reply to Mike Kaganski from comment #1) > 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". This point makes a lot of sense. The representation of a document should follow as much as possible its logical structure and, at least, never contradict this logical structure. > > 2. […] > > 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... A bit difficult to follow but I get the idea. I have already noticed some strange behaviour with multi-column pages. From some point of view, a multi-column page has a known vertical extent and this simplifies text flow (even with column balancing because this is done only after a page break, "natural" or manual, is inserted. A balanced multi-column section has a more "dynamic" handling, requiring rebalancing along text addition. Its vertical extent is not known and precautions should be taken. Non-nested sections (i.e. splitting a section to intersperse another one) is a good compromise. But I feel that truly nested sections, as done within multi-column pages) is also necessary, at least for consistency sake (and special applications). For the time being, I close this request as NOTABUG (feel free to change the status if not adequate). There are other issues with sections more urgent than this one, such as correct handling of vertical space above and below or perhaps correct handling of paragraph style vertical spacing (see bug 137069). Perhaps, the box model for sections is not correctly or thoroughly specified. Which ODF clause should I read to get an idea? -- You are receiving this mail because: You are the assignee for the bug.
