Unwanted page break in chapter heading

[Bremman]

Dear Forum Community,

Forgive me, but I am new and unsure of how to use this forum.

I am a self-publishing author and am creating an ebook using Calibre. I want to have my chapter headings such that the chapter number(s) appears above the chapter title(s), both of which are centered. This works out on all of my chapters except seven of them, and according to D2D validation tool, there are no errors.

The seven chapters that do not work out all have the chapter title: "A Primer on the Spiritual Life, Part...", and with each of these seven chapters, Calibre inserts a page break between the chapter number and "A Primer on the Spiritual Life, Part..." Can you help to remedy this, please?

I am using MS Word and uploading it into Calibre. Attached is the first of these chapter titles in the original Word document (Calibre - Forum 1). Also attached is the code in Calibre (Calibre - Forum 1 and 2).

Please help if you can.

Bremman

[theducks]

Something triggered a page split on file 21. There is no content in file 22 and 23 gives no clue why it split from 21 (if it did and not before you got the book)

In the Editor: Tools reports: Files: Sort (click the header) of Size:
Verify those HTML files with the tiny (and same) size and word counts, are those that are blank
Select and (right click) delete

[DNSB]

Originally Posted by theducks

Something triggered a page split on file 21. There is no content in file 22 and 23 gives no clue why it split from 21 (if it did and not before you got the book)

When I look at the two images, index_split_021 contains the chapter number by itself. I would suggest merging the two files (index_split_021 and index_split_022) instead of deleting index_split_021. See the Merging files item from the calibre ebook editor help. Repeat the merge as needed for the other split files.

[BetterRed]

Originally Posted by Bremman

. . .

I am using MS Word and uploading it into Calibre. Attached is the first of these chapter titles in the original Word document (Calibre - Forum 1). Also attached is the code in Calibre (Calibre - Forum 1 and 2).

It is because of the conversion settings :



See ==>> Structure detection and XPath tutorial

BR

[Bremman]

Thank you for your responses. I sincerely appreciate them!

I have been working at this ebook for most of the day and solved the problem by moving "Part..." to the next line in the MS Word document. Now Calibre does not separate the chapter number from the chapter title. I do not know anything about code, but it seems that the word "part" is a flag that causes a page break. I wonder what you think...?

Attached are two screenshots from two chapters of the seven that are now corrected. Thank you! I sincerely appreciate them!

[PeterT]

Originally Posted by Bremman

I do not know anything about code, but it seems that the word "part" is a flag that causes a page break. I wonder what you think...?

The part as a flag is what BetterRed was highlighting for you in their reply. The xpath mentioned in that post is used by calibre to detect and insert breaks.

Originally Posted by BetterRed

It is because of the conversion settings :

Attachment 216153

See ==>> Structure detection and XPath tutorial

BR

So just change the xpath expression to have xart rather than part.

[Bremman]

I found it!

Aside from knowing a few HTML commands to use on print-on-demand sites, I know next to nothing about code (although I figured out how to make my epubs error-free on Kobo's and Draft2Digital's validation tools).

To teach me something regarding code is an achievement!

Thank you all for your generosity!

PS -- What would happen if I deleted "part" rather than make it "xart"?

[theducks]

Originally Posted by Bremman

I found it!


PS -- What would happen if I deleted "part" rather than make it "xart"?

You just lose the ability to code a book to ALSO break at a New Part without repairing the standard keywords.

[JSWolf]

Originally Posted by theducks

You just lose the ability to code a book to ALSO break at a New Part without repairing the standard keywords.

What I've done when the default XPath causes a problem is to cut the XPath, do my conversion and then past it back.