https://bugs.documentfoundation.org/show_bug.cgi?id=152075
--- Comment #5 from Mike Kaganski <[email protected]> --- There are two ~orthogonal aspects: 1. Creation of a ToC *for the current part of the document*; 2. Inclusion of the entry that defines the current path into the ToC. IMO, the "flexible" proposal from comment 1 makes little sense. It is unreasonable to expect both levels higher than current in the local ToC, and also starting from levels lower than the immediate sublevels of the current one. So: when you have a section 2.4.6, and create a ToC under it, you might want to have 2.4.6 in the generated ToC, or you may want to have only 2.4.6.1, 2.4.6.2, ... . But you would not want entry 2 there, nor entry 2.4. In a strange situation when one could want these, one can always create cross-reference fields before the ToC, with specified levels. And one would not want the ToC to only contain 2.4.6.1.1, without 2.4.6.1 itself, in the ToC. All the extra situations are implementable using specific style assignment to the ToC, instead of basing the ToC on outline. One can even implement the layout requested in the mentioned Russian forum topic, using existing tools; bit since the requests to have ToCs for levels below 2, and also to omit the "starting" level, are really common, these *two* specific needs should be addressed in dedicated UI, but not an unlimited flexibility. So IMO: 1. The "Chapter" element must mean "current section" - which is already implemented in master, right? 2. There should be a [] Include current "chapter" into the ToC. The flexible "from level" selector is overkill, and is bad (would result in poor UX). -- You are receiving this mail because: You are the assignee for the bug.
