View Single Post
Old 04-04-2011, 06:52 PM   #23
DreamWriter
Books are brain food.
DreamWriter ought to be getting tired of karma fortunes by now.DreamWriter ought to be getting tired of karma fortunes by now.DreamWriter ought to be getting tired of karma fortunes by now.DreamWriter ought to be getting tired of karma fortunes by now.DreamWriter ought to be getting tired of karma fortunes by now.DreamWriter ought to be getting tired of karma fortunes by now.DreamWriter ought to be getting tired of karma fortunes by now.DreamWriter ought to be getting tired of karma fortunes by now.DreamWriter ought to be getting tired of karma fortunes by now.DreamWriter ought to be getting tired of karma fortunes by now.DreamWriter ought to be getting tired of karma fortunes by now.
 
DreamWriter's Avatar
 
Posts: 2,950
Karma: 4836916
Join Date: Nov 2010
Location: U.S.
Device: Paperwhite · Fire HD6/HD8/HD10 · Galaxy Tab A7
Quote:
Originally Posted by DaleDe View Post
It is a nice work-around but wouldn't it be even better if Amazon didn't need this at all. Either of the fixes should have worked by themselves. To require both is a bug.
Yes! There is no logical reason why my fix works, while using
Code:
<mbp:pagebreak />
or
Code:
page-break-before:always;
alone does not. I tried positioning things in many different ways too.

As I mentioned earlier, in the latest "Amazon Kindle Publishing Guidelines", on page 7 it states:

Text guideline #2: page breaks

Use the page break standard CSS page-break-before and page-break-after attributes.


There is no mention of
Code:
<mbp:pagebreak />
at all. I tried their suggestion alone, and it didn't work perfectly.

If anyone does comes up with a better (more logical) solution, I'm all ears.
DreamWriter is offline   Reply With Quote