Bug 118960 - Problem with tab stop right alignment or zero position in Table of Contents index / ToC for additional tab stops
Summary: Problem with tab stop right alignment or zero position in Table of Contents i...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
Inherited From OOo
Hardware: All All
: high normal
Assignee: Not Assigned
: 87523 99163 116009 (view as bug list)
Depends on:
Blocks: TableofContents-Indexes
  Show dependency treegraph
Reported: 2018-07-26 16:30 UTC by Timur
Modified: 2022-07-30 03:40 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:

TOC-alignment.odt (19.75 KB, application/vnd.oasis.opendocument.text)
2018-07-26 16:30 UTC, Timur
TOC-alignment fileopen compared LO MSO (158.07 KB, image/jpeg)
2018-11-27 09:45 UTC, Timur

Note You need to log in before you can comment on or make changes to this bug.
Description Timur 2018-07-26 16:30:36 UTC
Created attachment 143792 [details]

Alignment in Table of Contents issue was mentioned first in Bug 32360. I converted that bug to enhancement that's also requested. 
Later it was reported in Bug 87523. Somehow, it went wrong and closed, but I'll mark as a duplicate of this one. 
Again it was reported in Bug 90667 but let's keep that bug as a special case because it doesn't follow general problem from this bug. 
I'm turning this one into LO issue with right alignment in TOC. 

There's a general issue and issue with some docs. 
General issue is presented in attached ODT. It's about adding (Insert TOC) and editing TOC (right-click edit Index). 

If you add tab stop (before Chapter number), it will behave normally only if you add some Tab stop position (here 0,5cm). That's the first TOC.
But if you just add tab stop (let's say before Chapter number as in examples, but can be after also), it will have default tab stop position 0cm and be conflicted with another tab that's aligned right. That's the second TOC.

Expected: Chapter name Entry is always normally positioned after Chapter number, including if there's another tab (regardless if another tab is positioned 0cm or Right align, if that won't be changed)
Experienced: Entry is right aligned if we add second tab stop with default position 0cm or "Align right" while default tab stop before page number remains "Align right". 

- add tab position to first tab position (not likely to discover) and don't use "Align right" there (OK, not default)
- turn off right align from second tab (not what we want).
Note: adding for each level is different.
Comment 1 Timur 2018-07-26 16:32:03 UTC
*** Bug 87523 has been marked as a duplicate of this bug. ***
Comment 2 Timur 2018-07-27 12:07:48 UTC
*** Bug 99163 has been marked as a duplicate of this bug. ***
Comment 3 Timur 2018-07-27 12:13:43 UTC
Example attachment 124599 [details] from Bug 99163 shows the same: 3rd tab stop with tab stop position of the second level of 0cm. Didn't mention right alignment. 
New per duplicates. I mark earlier as a dupe, since more details here. Saw the other one only after reporting. Never mind, there was no activity. Hopefully this one will bump it now.

Real solution is to prevent unneeded right alignment. Partial solution is to set tab stop position to more than 0 and maybe disable 0.
Comment 4 Timur 2018-07-31 16:47:42 UTC
*** Bug 116009 has been marked as a duplicate of this bug. ***
Comment 5 Timur 2018-07-31 16:50:42 UTC
Example attachment 140138 [details] from Bug 116009 shows the same: 2nd tab stop with tab stop position 0cm in addition to right aligned. Didn't mention right alignment though. 
Similar suggestion to put a default value other than 0.
Comment 6 Thorsten Behrens (allotropia) 2018-11-26 12:28:30 UTC
Is that fixed with bug 121456 ?
Comment 7 Timur 2018-11-27 09:34:57 UTC
Not fixed with bug 121456. 
If example ODT is opened in MSO it previews similarly incorrect as in LO, but Update Field fixes it, unlike LO.
Comment 8 Timur 2018-11-27 09:45:42 UTC
Created attachment 147061 [details]
TOC-alignment fileopen compared LO MSO
Comment 9 QA Administrators 2019-11-28 04:08:01 UTC Comment hidden (obsolete)
Comment 10 Timur 2020-07-29 15:53:52 UTC
Repro 7.1+
Comment 11 QA Administrators 2022-07-30 03:40:56 UTC Comment hidden (noise)