If I create a table of contents before the first headline when the contents of the table are not taken from the capital-numbering, but from other templates, the table of contents starts with #2, not one. Maybe it's better, to show you the file and hope, you can reproduce this bug. Find the file attached and have a look at the second line in the table of contents. (number should be §2) Sry for my bad english, I can't describe this bug better :(
edit: the number of the second line in the table of contents on my pc is 2, but should be 1.... Describes this situation better. But maybe, you get a correct number in the second line in the table of contents Greetings Sam
Created attachment 40146 [details] Example for the Bug You can see the problem in the table of contents. The first headline "Allgemeines" has number "B". But in the document it's number "A" This headline doesn't belong to the outline of the document. It's only some kind of parting the document in smaller pieces for better looking. But I said, the table of contents shall contain it by "create table of contents from outline -> yes" and "create table of contents from other templates -> yes". Maybe this is a little more helpful.
I see the problem as well. The document is a bit strange: 1. "View/Navigator" does not list (A), (B), ... entries as headings. 2. "Tools/Outline Numbering..." has the paragraph style "Heading 2" for the level "1" I am not Writer expert but I think that the above settings affect the table of content generation. I do not understand how it was supposed to work. Anyway, I was not able to fix it by modifying "Tools/Outline Numbering..." Cedric, it might be for you.
Are there some news about this bug? If it's helpful to explain the (wished/requested) outline of the document, I would welcome the chance, to explain it, if there are some questions. Didn't tested the document with actual RC, so maybe the bug is also fixed. But I was just clearing up my pc, and stumbled over the example file for the bug.. So let me know, if I can help, or test something... Best regards, Samuel
This is a Writer bug, right? Therefore changed 'Component'.
Created attachment 62443 [details] TOC Example I have hit the same bug on Ubuntu 12.04 LibreOffice 3.5.3.2
If comment #6 is right, this is a cross-platform bug, therefore changed the Platform field accordingly.
Still REPRODUCIBLE with both sample documents and LibreOffice 3.5.5.3 (Build-ID: 7122e39-92ed229-498d286-15e43b4-d70da21), German langpack installed, on MacOS X 10.6.8 (Intel).
Still REPRODUCIBLE with LibreOffice 4.0.1.2 (Build ID: 84102822e3d61eb989ddd325abf1ac077904985) on Windows 7 x64
This bug has not been touched by its Assignee for a long time. To make it clearer which bugs should be fixed by someone else please take following action: - If you are the Assignee, and you are actively working on the bug, please give it an update. - If you are the Assignee, and you do not plan to work on it in the near future, please reassign it to the default assignee.
Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
LibreOffice 4.4.0.3 has this bug on Fedora 21 x86_64.
The first attachment comes from the conversion of a MS-Word file (numbering style named WW8Num1). It would be interesting to know if you can reproduce the problem from a completely empty .odt file from the default template. I think there is a mismatch between chapters numbering and adding a numbering to heading and text body styles. Best regards. JBF
Occurs back to OOo / LO 3.3.0 -> Version: Inherited from OOo
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Still exist. In TOC_Example document, only if place TOC in the end of the document numbering in TOC is ok (or anywhere after 1. Terms of References). Version: 5.4.0.0.alpha0+ Build ID: a296a69c984b17cfbcd249cf6bdc191d08dff2a6 CPU Threads: 2; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-02-06_00:00:55 Locale: bs-BA (bs_BA); Calc: group
(In reply to Jean-Baptiste Faure from comment #13) > The first attachment comes from the conversion of a MS-Word file (numbering > style named WW8Num1). If this is true, than this whole bug is not properly reported nor triaged. Exact steps are required to reproduce the issue. If the document was "converted" from MS-Word file, than the source file should be attached, with the steps and LO version used to convert it. Otherwise, this bug may stay open for a long time, without any real chance to be fixed. I don's see who confirmed the bug, but questions are not answered. So I'll revert this one to Needinfo. Please provide the answers and set back to Unconfirmed. If this can be reproduced from empty .odt file, without conversion, that's even better, but that should be clean new bug.
More observation in the example given for TOC bug: turn on navigation and the first address is: A) allgemeines (after mark it as Heading1) But when after the title on the first page vom TODO: Date I press two times enter appears A) and the navigation can be seen that the first title now B) After another ENTER A) in this text is lost, the title to the navigation returns to A)but most likely remain as such continues to TOC.
Created attachment 131590 [details] Another example of the TOC bug
I can add some information to this, because I think I have encountered the same bug in a different setting. My problem seems to relate to (ab)using outline numbering to number paragraphs, i.e. Level 1 is Heading 1, but Level 2 is associated with the Text body style, which I do in order to get the chapter number into the individual paragraph numberings. Example document is being attached. Even though there are no instances of either Heading 1 or Text body before the first header, this seems to throw off display of the TOC, which starts at § 2. Do note that if you hover over the TOC, the correct link text is displayed. Also, as the original poster said, this is only a problem if the TOC appears before the first instance of Heading 1.
The file I just attached is a native ODT I created just to reproduce this bug, so it seems to be independent from the Word conversion.
I can confirm the behavior listed in Comment 20 from creating a new file in Writer 5.1.4.2 using just H1's and Text body paras with H1 assigned to Level 1 numbering and Text Body style assigned to Level2 numbering so that each paragraph is numbered and picks up the Chapter number. If an empty text paragraph is positioned between the ToC and the Document text/headings, then the ToC displays correctly.
Philip also found out that the paragraph between ToC and the first heading needs to be (a) of style "Text body" (i.e. outline-numbered in the way we use outline numbering to number paragraphs), and (b) numbering needs to be turned off with F12 for this paragraph. If both (a) and (b) are in place, then the ToC displays correctly. The discussion is here: https://www.mail-archive.com/users@global.libreoffice.org/msg51172.html
Dear Bug Submitter, 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-20170830
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20170929