keep header with following text

[RbnJrg]

Originally Posted by PilcrowandStanza

THIS WORKED!!
thank you so much!

You are welcome

Yes, this is for a book with 2nd level headers (more than just chapter titles) that has to continue from the text above, can't just break to a new page.

The property "page-break-after: avoid" controls page breaks on ereaders based on RMSDK and properties "break-after: avoid" and "-webkit-column-break-after: avoid" control page breaks on ereaders based on Readium/Webkit. So, unless your e-reader is very poor at handling epubs (like CoolReader), using the published style will prevent unwanted page breaks wherever you include it.

Originally Posted by RbnJrg

Employ the following style:

1. In your .css stylesheet:

.noBreakAfter {
    -webkit-column-break-after: avoid; /* This is for epub3, epub2 ebooks will ignore it */
    page-break-after: avoid; /* This is for epub2; epub3 ebooks will ignore it */
    break-after: avoid; /* Also for epub3 */
}

2. In your .xhtml:

<h2 class="noBreakAfter">Your title here</h2>

<p>Your following text here ... </p>

[jugaor]

Hello everyone.

I've been using both lines for many years:

page-break-after: avoid;
break-after: avoid;

(in that order) with success in all tests (except, of course, the limited Cool, FBReader, Readera, etc.).

That's why this remark intrigues me:

Originally Posted by RbnJrg

and now ereaders based on webkit/readium finally gave support to "-webkit-column-break-after: avoid"

@RbnJrg, what devices or apps have you found that work with -webkit-column-break-after and don't honor break-after ? (I haven't found any yet.)
Since I prefer to avoid proprietary instructions (unless absolutely necessary), is this really necessary or are you just being overly protective?

Gracias!

[RbnJrg]

Originally Posted by jugaor

Hello everyone.

I've been using both lines for many years:

page-break-after: avoid;
break-after: avoid;

(in that order) with success in all tests (except, of course, the limited Cool, FBReader, Readera, etc.).

That's why this remark intrigues me:

@RbnJrg, what devices or apps have you found that work with -webkit-column-break-after and don't honor break-after ? (I haven't found any yet.)
Since I prefer to avoid proprietary instructions (unless absolutely necessary), is this really necessary or are you just being overly protective?

Gracias!

All Android applications that support epub3 (Cantook, Kobo for Android, Reasily, Lithium, Infinity Reader, PocketBook, BookFusion, the old Gitden -but now is not working with modern Androids) will only honor
-webkit-column-break-after, -webkit-column-break-before and -webkit-column-break-inside. Also Thorium, Koodo Reader and ADE 4.x for PC and Foliate for Linux need those properties in order to handle page breaks.

The properties you mention are honored by ADE 2.x/3.x (ADE Legacy, that employs RMSDK), ereaders based on RMSDK and Calibre Viewer. Tolino Shine 5 needs the webkit properties. So, in order to cover al posibilities, employ always:

.noBreakAfter {
    -webkit-column-break-after: avoid;
    page-break-after: avoid;
    break-after: avoid;
}

Y nada que agradecer

[ElMiko]

Apologies for derailing the topic @RbnJrg, but the footnoted philosophy text you posted has me in a tizzy. How are the footnotes footnotes being incorporated into the main body text like a physical book (rather than as a pop-up or a link to a separate html sheet)???

[Jellby]

I think that's a KOReader feature.

[ElMiko]

@Jellby - Thanks. Also... sadness.

[RbnJrg]

Originally Posted by ElMiko

Apologies for derailing the topic @RbnJrg, but the footnoted philosophy text you posted has me in a tizzy. How are the footnotes footnotes being incorporated into the main body text like a physical book (rather than as a pop-up or a link to a separate html sheet)???

It's as Jellby says, a KOReader feature. For epubs without images and with undemanding layouts, KOReader (an epub2 e-reader) is one of the best.

[DNSB]

You can use footnotes in a chapter using standard ePub3 features. KOReader is not needed.

[ElMiko]

@DNSB - Roger that. But to get that effect in epub2, that's dependent on the rendering software (eg KOReader)?

[DNSB]

Originally Posted by ElMiko

@DNSB - Roger that. But to get that effect in epub2, that's dependent on the rendering software (eg KOReader)?

And that's why I avoid in chapter footnotes like the plague even if they are displayed at the end of the chapter.

On the tilting at windmills side, I once spent way too much time trying to get footnotes to display at the bottom of the referencing page in a couple of Terry Prachett ebooks in a failed attempt to make them look more like the paper books. In my defence, I was watching various dashboards on graveyard shift with an occasional break to setup or rebuild systems. While this needed to be done, it gave too much time for idle hands.

[Slevin#7]

In the ebooks I'm currently responsible for we have a bunch of footnotes. I've decided to put them directly under the regarding paragraph, since in our case they almost carry additional important information and having them near by the footnote mark makes it easier to read without jumping round the ebook forth and back.

The foontnotes itself have a slighter smaller font-size, sans-serif in contrast to the serif main text, and a dedicated background color of #f6f6f6 to mark the section as a whole. That's for now the best solution I've come up.

[RbnJrg]

Originally Posted by Slevin#7

In the ebooks I'm currently responsible for we have a bunch of footnotes. I've decided to put them directly under the regarding paragraph, since in our case they almost carry additional important information and having them near by the footnote mark makes it easier to read without jumping round the ebook forth and back.

The foontnotes itself have a slighter smaller font-size, sans-serif in contrast to the serif main text, and a dedicated background color of #f6f6f6 to mark the section as a whole. That's for now the best solution I've come up.

On epub3, you don't need to jump anywhere; the endnotes will be displayed in a popup window. Unless, of course, you are speaking about epub2 endnotes/footnotes.

[JSWolf]

[QUOTE=PilcrowandStanza;4527651]THIS WORKED!!
thank you so much!

Yes, this is for a book with 2nd level headers (more than just chapter titles) that has to continue from the text above, can't just break to a new page.

Originally Posted by RbnJrg

Employ the following style:

1. In your .css stylesheet:

.noBreakAfter {
    -webkit-column-break-after: avoid; /* This is for epub3, epub2 ebooks will ignore it */
    page-break-after: avoid; /* This is for epub2; epub3 ebooks will ignore it */
    break-after: avoid; /* Also for epub3 */
}

2. In your .xhtml:

<h2 class="noBreakAfter">Your title here</h2>

<p>Your following text here ... </p>

You should never use webkit code. It's not part of ePub. You need to redo your code so there is nothing about webkit present.

[Turtle91]

Originally Posted by JSWolf

You should never use webkit code. It's not part of ePub. You need to redo your code so there is nothing about webkit present.

I disagree completely. A standards compliant reader/device/app will gracefully ignore anything it doesn't understand. If you include items like webkit selectors the reader will use them if it can, and ignore them if it can't.

.noBreakAfter {
    -webkit-column-break-after: avoid;
    page-break-after: avoid;
    break-after: avoid;
}

This is simply trying to cover all the bases for all the different types of devices.

You may run into issues where an older automated epub checker could throw a flag saying it isn't an ePub selector, but that wouldn't make the ePub invalid.

If your targeted device/app supports it, and you want/need it to do what you need, then go for it!