Bug 90667 - Problem with alignment in index / TOC in specific DOT (per Comment 10)
Summary: Problem with alignment in index / TOC in specific DOT (per Comment 10)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: Other All
: low normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: DOC-TableofContents
  Show dependency treegraph
 
Reported: 2015-04-17 02:37 UTC by gon_aranda
Modified: 2023-06-30 03:13 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
The step to reach the bug. (114.94 KB, image/png)
2015-04-17 02:37 UTC, gon_aranda
Details
One of the files I notice the bug. (51.50 KB, application/msword-template)
2015-04-19 04:08 UTC, gon_aranda
Details

Note You need to log in before you can comment on or make changes to this bug.
Description gon_aranda 2015-04-17 02:37:50 UTC
Created attachment 114845 [details]
The step to reach the bug.

The index has some problems with the tabulation. I got a document in MSOffice with index and when I tried to edit it in Open and update the index it brokes, the tabs dissapears.
When I try to put manually using the index editor with another tab the "Tab position relative to paragraph style indent" doesn't work.

Sorry for my english.
Comment 1 Buovjaga 2015-04-18 12:01:40 UTC Comment hidden (obsolete)
Comment 2 gon_aranda 2015-04-19 04:08:44 UTC
Created attachment 114899 [details]
One of the files I notice the bug.
Comment 3 Buovjaga 2015-04-19 07:19:51 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2016-09-20 09:24:57 UTC Comment hidden (obsolete)
Comment 5 Timur 2018-07-18 13:56:35 UTC Comment hidden (obsolete)
Comment 6 Xisco Faulí 2018-07-25 08:17:53 UTC Comment hidden (obsolete)
Comment 7 gon_aranda 2018-07-25 15:49:31 UTC
First, when you load the file the index is

1.<tab><Title><tab><page_number>

That is the desire outcome, but in the index configuration it never has the first tab. That’s why when you update the index the first tab dissapears. So I think the bug would be loading .dot files with index you lose some settings. In this case, you lose the first tab in every level. When I tried to added it manually all broke because you also lose the “align right” from level 3 and above of the second tab (and I didn't notice).

The ideal would be that these settings load automatically and you could update without losing format.

I get the desire outcome making this modifications:

- Adding a tab between E and E# in every level, with tab stop at 0.8, 1.6 and 2.5 cm for the first three levels
- Adding “align right” for the second tab from 3 level to above.
Comment 8 Timur 2018-07-26 15:35:52 UTC Comment hidden (obsolete)
Comment 9 Timur 2018-07-26 15:46:07 UTC Comment hidden (obsolete)
Comment 10 Timur 2018-07-26 16:31:22 UTC
Default TOC in LO is also another issue, there's bug 32360. 
Another bug or two would be that LO "recognizes" TOC structure from DOC and DOCX so that it can be edited further. 
Here we deal with alignment in index / TOC.

There's a general issue and issue with some docs. 
I'll report the general issue separately, but I confirm issue with this DOT. 
Normally if you add another tab stop as it was done here, it will behave normally if you add some Tab stop position (here 1,0cm).

1. Open .DOT to get new document
2. Go to "Table of Contents" on page 3 and right-click Edit Index
3. Go to level 2
4. Between E# and E add "Tab Stop" with "1 cm" position
5. OK
6. Right-click Update Index

Expected: Chapter name Entry is left aligned after 1 cm tab. 
Experienced: Entry is right aligned. 

I kindly ask others to evaluate this bug in the light of general issue Bug 118960.
Comment 11 Timur 2018-07-27 14:10:41 UTC
I reported general LO issue as Bug 118962. 
There I wrote that behavior for MS created documents is slightly different. 
This bug is an example. 
Problem comes from "Tab Stop" with "1 cm" position that's not enough. Increasing solves it.
Comment 12 QA Administrators 2019-08-03 03:05:44 UTC Comment hidden (obsolete)
Comment 13 Timur 2019-08-28 08:06:31 UTC
Repro 6.4+
Comment 14 Stéphane Guillou (stragu) 2021-06-29 10:00:36 UTC
Reproduced as in comment 10 with:

Version: 7.3.0.0.alpha0+ / LibreOffice Community
Build ID: f446a203fa2897bab8ae7686c948a8bf060675c6
CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-06-24_15:16:38
Calc: threaded
Comment 15 QA Administrators 2023-06-30 03:13:34 UTC
Dear gon_aranda,

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 with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

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) from https://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: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug