Problem with Page Breaks and Structure Detection

[cjallan]

Originally Posted by jackie_w

What is the NCX view? I just used Goto TOC in Kindle-for-PC plus I opened the mobi in the Calibre Viewer. Both of these seemed to be OK. Is NCX view something else? I don't have a Kindle so I'm not familiar with the finer details.

Yes, the NCX file is something else... and is an Amazon requirement.

When you display a Kindle file with the Kindle Previewer, look at the two little icons at the right end of the Menu Strip.

Click the very last icon to display the NCX view...

Click the next to the last to display the TOC that was built by Calibre.

[jackie_w]

@idolse & cjallan,

OK, thanks for explaining. I guess I'll drop out of this thread at this point as I've never needed to install Kindle Previewer and I can't think of anything else to suggest.

[cjallan]

Jackie_W,

The NCX view is "required by" Amazon for Kindle eBooks, but they are not currently enforcing that requirement.

It can be displayed by clicking the last icon at the menu strip at the top of the Kindle Previewer. (see screen shot).

Thanks for creating that very effective MobiTest File.

With it, I was able to sort out my real problem, which is:

Calibre, at default, creates a page break before H2.

When there is no body text immediately after the title for H1, that leaves the entire rest of the page blank.

(see screen shot)

Then H2 starts on the next page.

If I try to remove that page break before H2, I create problems with the proper display of H1 and H2 in the NCX file.

I have attached the mobi file created from your mobitest.

Thank you... and thank you to the others who are helping!

CJ

[jackie_w]

Perhaps you could make life easy for yourself and learn to love the H1s being on a page of their own

Is this really so bad? Many novels I read which are structured:

Part 1
     Chapter 1
     Chapter 2
     etc...
Part 2
     Chapter 1
     Chapter 2
     etc...

have their Part headings on their own page.

[cjallan]

Originally Posted by jackie_w

Perhaps you could make life easy for yourself and learn to love the H1s being on a page of their own

Is this really so bad? Many novels I read which are structured:

Part 1
     Chapter 1
     Chapter 2
     etc...
Part 2
     Chapter 1
     Chapter 2
     etc...

have their Part headings on their own page.

You are right... that doesn't look bad at all!

Thanks again,

CJ

[theducks]

Originally Posted by jackie_w

Perhaps you could make life easy for yourself and learn to love the H1s being on a page of their own

Is this really so bad? Many novels I read which are structured:

Part 1
     Chapter 1
     Chapter 2
     etc...
Part 2
     Chapter 1
     Chapter 2
     etc...

have their Part headings on their own page.

I lean toward this:
What I hate is when the publier coding results in:

Part 1
     Chapter 1
Chapter 2
etc...
Part 2
     Chapter 1
Chapter 2
etc...

[jackie_w]

@theducks,

When this happens to me I just use this handy little epub utility to edit the TOC. It's a drag-and-drop action so very easy to use.

[theducks]

Originally Posted by jackie_w

@theducks,

When this happens to me I just use this handy little epub utility to edit the TOC. It's a drag-and-drop action so very easy to use.

TNX
I think I tried a early version of this tool a long time ago and abandoned it I was learning about EPUB).

Been fixing this issue, along with other odd coding with Sigil (CV)

I could us a de-spanner that only removes un-necessary repeated spans

<span="foo2">stuff</span><space><span="foo2">more stuff</span>

Must pair-match tags before cleaning. (A simple REGEX does not match pairs and can really make a pile of doo out of things.)