Download it now!
Bug 70451 - Add ToC / Table of contents option to respect or not new lines / line breaks in headings
Summary: Add ToC / Table of contents option to respect or not new lines / line breaks ...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.0.4 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: TableofContents-Indexes
  Show dependency treegraph
 
Reported: 2013-10-14 12:21 UTC by devseppala
Modified: 2019-10-24 11:51 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
Line breaks are not included in the table of contents with LO 4.1.2 (8.88 KB, application/vnd.oasis.opendocument.text)
2013-10-14 12:30 UTC, devseppala
Details

Note You need to log in before you can comment on or make changes to this bug.
Description devseppala 2013-10-14 12:21:09 UTC

    
Comment 1 devseppala 2013-10-14 12:26:54 UTC
Table of contents does not respect line breaks in headings and removes them. This is a regression from the 4.0.x series where the line breaks are included in the table of contents.

I have attached an example file. Try to update the table of contents in the second page and you will see that all of the entries are on one line. If you look at the actual Headings on the next page, you will see that there is a line break in the second heading.
Comment 2 devseppala 2013-10-14 12:30:03 UTC
Created attachment 87596 [details]
Line breaks are not included in the table of contents with LO 4.1.2
Comment 3 devseppala 2015-04-03 16:53:49 UTC
Small situation update:

The bug is still present in LO 4.4.2

I was able to trace the earliest affected version to 4.1.0.0.beta1

http://downloadarchive.documentfoundation.org/libreoffice/old/4.1.0.0.beta1/win/x86/LibreOfficeDev_4.1.0.0.beta1_Win_x86.msi.mirrorlist

This means that bug was introduced by one of these changes:

https://wiki.documentfoundation.org/Releases/4.1.0/Beta1

I am not able to recognize from the descriptions which change is the culprit.
Comment 4 devseppala 2015-04-03 17:34:36 UTC
After going though the changes in 4.1.0.0.beta1. I found out that this behaviour (bug) was introduced on purpose by this change.

https://bugs.documentfoundation.org/show_bug.cgi?id=61458

I disagree with the motivation of this change and think that it should be reverted. The previous behaviour was in place for a long time and for example in my organization we have relied on this in formatting in our documents.

I have to check how this is handled in other word processors.
Comment 5 devseppala 2015-04-07 20:01:49 UTC
I checked that the competing word processor also removes newlines from paragraphs when building the TOC, so now the new behaviour is compatible with it. This probably means that this is a "WON'T FIX"-issue.

However, the other software has a "Just update page numbers"-feature, which makes making custom changes to the TOC much easier. As writer does not have this, all changes you make to TOC (ie. manually insert the missing new lines) are lost, if you have to rebuild the TOC.

As the old behaviour had been in place for a long time, it would have been preferable if this change would have been implemented together with a configurable variable in TOC-settings. A simple check box "keep newlines".
Comment 6 tommy27 2016-04-16 07:23:27 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2017-05-22 13:23:27 UTC Comment hidden (obsolete)
Comment 8 devseppala 2017-05-29 10:39:10 UTC
This bug is still present on LO 5.3.3.

As previously said, "Just update page numbers"-feature in updating the index would be helpful in going around this bug.
Comment 9 QA Administrators 2018-05-30 02:38:54 UTC Comment hidden (obsolete)
Comment 10 Timur 2018-08-01 16:37:07 UTC
I find this request legitimate, but not to revert, but to add ToC / Table of contents option to respect or not new lines / line breaks in headings.
That's how it should've been done in first place.
Comment 11 devseppala 2019-10-24 11:51:14 UTC
Just confirming that this behaviour is still in LO 6.3.3. I also agree with Timur, that there should be a TOC option for this.