Bug 116009

Summary: Tabs stops on TOC dont respect independent alingnment
Product: LibreOffice Reporter: Andre Cabral <cabral.bh>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: ilmari.lauhakangas
Priority: medium    
Version: 6.0.1.1 release   
Hardware: All   
OS: All   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: TOC tabstop exemple
exemple of secund coment

Description Andre Cabral 2018-02-25 18:29:16 UTC
Created attachment 140138 [details]
TOC tabstop exemple

when inserting a tabstop between chapter number and entry text, you uncheck the left alignment or mark a fixed distance.
However at the time the TOC is generated, this formatting is ignored with the left alignment as well, such as the tabstop between entry text and page number.

in version 5.4.2.2 this does not happen.
Comment 1 Andre Cabral 2018-02-25 18:52:07 UTC
Created attachment 140139 [details]
exemple of secund coment
Comment 2 Andre Cabral 2018-02-25 18:53:30 UTC
with a little more research I realized that the problem may not be exactly a bug, but a pre-setring problem in the value of the Tab stop position frame. If you keep the value 0.0cm, all the TOC is messed up, but if you put a value above 0.7cm the TOC assembly starts to come out correct.
would not it be the case to put a default value other than 0 to avoid misinterpretation?
Comment 3 Buovjaga 2018-03-08 14:18:38 UTC
(In reply to Andre Cabral from comment #2)
> with a little more research I realized that the problem may not be exactly a
> bug, but a pre-setring problem in the value of the Tab stop position frame.
> If you keep the value 0.0cm, all the TOC is messed up, but if you put a
> value above 0.7cm the TOC assembly starts to come out correct.
> would not it be the case to put a default value other than 0 to avoid
> misinterpretation?

If you want feedback, I think you should give more detailed steps on what we should do with your files. Also include screenshots of the bad and good results.
Comment 4 Timur 2018-07-31 16:47:42 UTC
Only when I reported a similar bug I saw there were reports but incomplete.
This one had a nice example.

*** This bug has been marked as a duplicate of bug 118960 ***