Case: I want to have the chapter number of second-level entries to have the same indent (be aligned with) the chapter number the first-level entries.
- Insert index when there's multiple levels of headings in the document
- set tab stop position of the second level to 0 (zero), click ok
- the ToC looks garbish as the indent of the second level seems to be 1.55 rather than 0
Whether 'Tab position relative to paragraph style indent' is selected or not does not seem to make a difference.
I can add the document in which this is the case, if necessary. It concerns a 'native' odt document (newly made from LO)
Build ID: 1:5.1.1~rc2-0ubuntu1~trusty0
CPU Threads: 4; OS Version: Linux 3.13; UI Render: default;
Locale: en-GB (en_GB.UTF-8)
Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug.
I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document.
(Please note that the attachment will be public, remove any sensitive information before attaching it.)
How can I eliminate confidential data from a sample document?
Created attachment 124599 [details]
Sanitised document with the bug
2nd level ToC entries: tab stop position set to 0.05 cm currently
changing it to 0.00 cm renders the error
Right-click ToC - Edit index - Entries - Level 2 - Tab stop: input 0 for position.
I reproduce with document.
Win 7 Pro 64-bit Version: 184.108.40.206.alpha1+
Build ID: 3d27afd26f7b85c46a7c7d08498000b9dbcea1c8
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default;
TinderBox: Win-x86@42, Branch:master, Time: 2016-05-09_02:42:15
Locale: fi-FI (fi_FI)
Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735
** 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.2.7 or 5.3.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)
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!
ONly when I reported a similar bug I saw this one.
Since I have more details, I'll mark this one as a dupe and confirm the other.
*** This bug has been marked as a duplicate of bug 118960 ***