For a complete description, see here:
Solving this report is important for complete control of TOC's layout.
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
The feature requested is not implemented on 3.5 beta2 yet.
Apache OO issue (from comment #0) added to See Also list.
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:
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
Shortcoming re-confirmed under Debian 7 x86_64 using:
v188.8.131.52 Build ID: 48d50dbfc06349262c9d50868e5c1f630a573ebd
v184.108.40.206 Build ID: bc356b2f991740509f321d70e4512a6a54c5f243
Insert > Indexes and Tables > Indexes and Tables... > Entries tab > Structure and Formatting section > Structure list > click [T] tab entry > "Tab stop position" and "Align right" are the only (mutually exclusive) sub-options. It would be better to simply have the usual (ruler) tab icon button to cycle through via clicking, rather than an "Align right" option.
Related AskLO thread: http://ask.libreoffice.org/en/question/30542/
Created attachment 123860 [details]
Attached is a test document that shows the problem. See description in the document: three TOCs are build as example and a "pseudo TOC" shows how TOC should look like.
There are 2 issues here, if I understood well:
1. Enhancement request from description to change default TOC to be:
("index link“), “tab stop” right aligned (like 0,5cm), “chapter number”, “tab stop” left aligned (like 1cm), “chapter name entry”, “tab stop” right aligned (like 17cm), “page number”, ("end").
Current LO default is:
"index link“, “chapter number”, “chapter name entry”, “tab stop” right aligned, “page number”, "end".
I change the title here to:
Change default TOC entries to include tabstops before and after "Chapter number" entry
This request needs to be evaluated for benefit it would yield.
2. Bug from title and attachment that "tabstops on TOC are no fully functional (do not support right and middle alignment)".
That's not correct description, because they do support alignment, albeit not properly. This is a separate issue and I'll See Also that.