[Solved] ToC treats embedded line break as 2 lines

[EdIsenberg]

I've finished a SF novel that will be printed in a "Trade Paperback" format: 6" x 9". Several of my Chapter Titles are too long to fit on one 4.5"-wide line, so I broke them up into two physical lines with a line-break (Shift-Enter). The Table of Contents erroneously reads the Chapter Title as two lines / 2 Chapters:

In my text the following is centered:
Chapter 19: Cyborgs, Money, UFOs, Insanity, and Sex

After I use a line break it appears in the text, centered,
Chapter 19: Cyborgs, Money,
UFOs, Insanity, and Sex

In the Table of Contents, it reads as follows:
Chapter 19: Cyborgs, Money,......................174
UFOs, Insanity, and Sex............................174

What I want in the ToC is:
Chapter 19: Cyborgs, Money,
UFOs, Insanity, and Sex............................174

I would greatly appreciate any advice. One idea is that maybe Shift-Enter isn't the right way to make a line-break.

[floris v]

I can't duplicate that. In Libre, the Line break is ignored, in AOO the break is kept, giving exactly the effect that you want. I can only get your effect if I insert a paragraph break in the heading, so maybe you thought you had hit Shift + Enter when in fact you just hit Enter.

[acknak]

I wonder if perhaps the "line break" you mention has actually come from pressing the Enter key, not Shift+Enter. Shift+Enter in the chapter title will insert an actual line break, which will give one entry in the ToC. Pressing Enter in the chapter title will indeed start a new line but it inserts a paragraph break, which then goes into the ToC as two separate headings.

It may be that the line break (Shift+Enter) carries into the ToC, so that may not be quite satisfactory either.

[RoryOF]

Whether it is a line break (shift Enter) or not can be confirmed by looking at the actual chapter title in the text and turning on /View /nonprinting characters. If it is a line break this will show as a left pointing hooked arrow.

[EdIsenberg]

Thanks for the help; using Enter instead of Shift-Enter was the problem. Such a stupid mistake on my part.

I appreciate your quick help. I wasn't able to send you a timely response because both my wife & I are disabled and in a lot of pain, so our "up" time is very irregular and we fall behind on stuff quite easily. I do have other questions which I will post after double-checking that neither I nor this forum has the answer available.

Ed