View Single Post
Old 07-25-2025, 12:18 AM   #5
RbnJrg
Wizard
RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.RbnJrg ought to be getting tired of karma fortunes by now.
 
Posts: 1,815
Karma: 8700631
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
Quote:
Originally Posted by Quoth View Post
Only starting a new file at a header works on everything.
Yes, of course. But there may be subheadings within a single chapter that, if they start on a new page, could disrupt the flow of the story. In these cases, it's helpful to have a way to avoid a page break immediately after those subheadings. ADE 2.x honors "page-break-after: avoid" since always and now ereaders based on webkit/readium finally gave support to "-webkit-column-break-after: avoid", so virtually any halfway decent e-reader can avoid a page break after a heading.

But there are still some "tricks" that allow you to avoid page breaks even without appealing to those properties, with simple CSS 2.0 declarations (that is 1998, the prehistory of CSS) that work on any e-reader that supports the margin and padding properties (and I find it hard to imagine that there is an e-reader that doesn't support them).
RbnJrg is online now   Reply With Quote