View Single Post
Old 03-25-2012, 11:28 AM   #8
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 27,549
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
The mobi pagebreak is now deprecated, and we are urged instead to use CSS. Here is mine:

p.breakhere {
page-break-before: always
}

Then in the text, <p class="breakhere">
Deprecated and urged by whom? Kindlegen (and all other programs that build MOBIs) will take the CSS you provided and convert it directly to <mbp:pagebreak/> in the resulting Mobi's internal markup. Unpack any brand-new mobi file and you will find scads of <mbp:pagebreak/> scattered throughout. That's because excluding the new KF8 format, MOBI still doesn't do CSS. At all. All the CSS is converted (by kindlegen et al) into html 3.2 attributes, and mobi-specific tags like <mbp:pagebreak/>

Your code example will convert fine, and will achieve the same goal, but both techniques are going to result in a <mbp:pagebreak/> tag in the long run. ;)
DiapDealer is offline   Reply With Quote