In "ordinary" documents, sections can be nested arbitrarily. There are two ways to create sections: from scratch with menu Insert>Section then populate it with contents, or select some existing contents and menu Insert>Section. Both work fine. When working with master documents, sub-documents seem to be managed as implicit sections (with a somewhat different semantics, though, as they appear both in the Navigation and Master views of the Navigator). Sections are not only used to temporarily change the geometry of the page (mainly number of columns) but also to change the location of the endnotes. In this latter role, a section may be needed to span several subdocs so that the endnotes are listed at a specific location according to author's wish. Unfortunately, there is no way to add a subdoc inside a section (the Master view in the Navigator only lists a sequence of subdocs, text and indexes without details on document structure). Alternatively, selecting the "range" and trying method 2 above fails because menu Insert>Section is disabled. I understand that obviously sections and subdocs must be properly nested, i.e. a section can't start outside sub-docs and end inside a subdoc and vice versa, but this is guaranteed by the fact that user does not set manually start and end section boundaries. Is there any restriction in ODF about it? Is there an intrinsic difficulty in the code which would forbid this possibility? This request for information may eventually be changed to a feature request. For some context see question https://ask.libreoffice.org/t/where-in-lo-master-endnotes-are-stored-and-how-to-rearrange-the-position/78542 (where I was wrong in my initial answers).
UPDATE: I tried to patch contents.xml in the master file to move end section boundary. The subdoc sections are then correctly nested inside the "outer" section as shown in the Navigator and section properties dialog but subdoc files are no longer listed in the Master view. Also endnotes don't appear at end of "outer" section but at end of each subdoc "section" (which is now nested inside the "outer" section). If I don't nest subdoc, endnotes are displayed at end of document (but this is not the location I want for them). So moving manually </text:section> damages document structure in unpredictable ways.
(In reply to ajlittoz from comment #0) > Unfortunately, there is no way to add a subdoc inside a section (the Master > view in the Navigator only lists a sequence of subdocs, text and indexes > without details on document structure). I tried to create a section in a master document, then inside it, create other sections, and link each of those inner sections to external documents. That worked fine for me. Then I added some endnotes in the subdocuments, and when back in the master documents, they gathered in the end of the main document (as expected). Then I tried to change the properties of the *outer* section (containing the inner linked sections-subdocuments), so that the outer section gathers endnotes at the end of the section. And that didn't affect the endnotes from subdocuments. I suppose that here, you have the latter observation as the problem you likely want to change; and also something in the UI that would help you create the nesting (that, as said, works manually).
(In reply to Mike Kaganski from comment #2) > I tried to create a section in a master document, then inside it, create > other sections, and link each of those inner sections to external documents. > That worked fine for me. Would you be so kind as to attach your document so that I can study the inner links. I was not able to do it myself (through the UI). I made other experiments: - sub-docs contain absolutely no section - when I patch (this may not be done correctly) contents.xml to move the end section boundary past the sub-docs, I end up with nested sections: the outer one and the sub-docs inside - the sub-doc sections have their "collect endnotes at end of section" automatically checked - if I uncheck the box, I crash Writer when I click OK to leave section properties (not section Options) Reminder: I'm running LO 7.4.3.2 under Fedora 36
Don't get the point. Insert a section, mark some text within the section and insert section for this paragraph. It becomes a nested section, and is shown as such in the dialog.
(In reply to Heiko Tietze from comment #4) > Don't get the point. The point is not with nesting sections. This works fine. The point is about having sub-documents inside a section with the goal to list the endnotes at end of this section. This would allow to have other text after the endnotes instead of having the endnotes as the very last element in the document. The specific placement of endnotes is a requirement from the patrons of OP in AskLO. There seems to be an incompatibility between sections and subdocs. Subdocs are only tolerated at top level.
Created attachment 181120 [details] Master + subdocuments
Created attachment 181121 [details] How I created that
Confirmed. @Heiko Tietze: in regular science books with notes and alphabetical index, the endnotes always precede the alphabetical index. In a single Writer document with the complete text of a book, you can put all content coming before the alphabetical index in a section to force the endnotes to come at the end of that section. In a masted document, you can't do that, which kind of defeats the purpose of having a master document for book manuscripts with endnotes and alphabetical index. In the present implementation, you can even have a heading over the endnotes. It would be very much better if the container for the endnotes were a field that the users can insert wherever they like, just as you can already do for the alphabetical index (which doesn't make sense because that will come at the very end of the document anyway). But changing that will probably mean changing the ODF specification.
(In reply to Mike Kaganski from comment #7) > Created attachment 181121 [details] > How I created that I see now that a sub-document is "just" a special kind of section (and the UI -- Navigator Master view or menu Insert>Section -- does not allow all possible variants). Then there is no way to move the endnotes into an outer section because "collect at end of section" will happen at the first section boundary, i.e. the sub-doc boundary. (In reply to Peter Roelofsen from comment #8) >It would be very much better if the container for the endnotes were a field >that the users can insert wherever they like I think that would potentially create problems (but I never read source code) as footnote and endnotes are likely managed the same. Footnotes can be set at bottom of page (field in this case is meaningless), at end of section or end of document. The two latter cases can be unified with endnotes if a field is created. But how do we update a note if it becomes a field? Today it is as simple as overwriting text.
Ajlittoz, almost two years after the last comment, I'd like to ask, if the request is stil valid. If this is the case, please tray to describe the problem in just a view steps like: 1. Open master1.odm from attachment 181120 [details]. It contains a section (section1) in the master document itself, that has two nested sections (subdocuments of master document). Each document has an endnote. Actual result: Endnotes are collected at end of master document Proposal: Provide possibility to place endnotes at end of the section (subdocument) Ajlittoz, is description correct? As far as I can see, we have the same behaviour in a normal document with sections / nested sections. So not only related to master documents. Dio you agree? => NEEDINFO
Dear ajlittoz, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping