Thread: Mobi & AZW Page Break NOT working
View Single Post
Old 11-11-2014, 03:18 PM   #36
Hitch
Bookmaker & Cat Slave
Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.
 
Hitch's Avatar
 
Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
Quote:
Originally Posted by pdurrant View Post
A new file isn't the only way to create a page break in an ePub. Using CSS and pagebreakbefore should work fine.
Paul:

I think that for mobi, we're still using separate pages/files for "breaks." Now, it could be that we're just stuck in a rut, but I think...nope, I'm pretty sure that even now, for mobi, the only way to get headings right, on the "page" (so to speak) is to use new files.

Now, I can see that this might be distressing for someone trying to assemble 500 recipes. Wendy, does the placement of the "top" of the recipe really matter to you? Do you care if it's precisely 3 lines down from the top of the screen, or is that a secondary concern? (This is about the eventual mobi-fication of her book, to be clear).

I would note, from a user-standpoint, that for rendering, the more files the merrier, in terms of snappy loading times. This is true for both ePUB and MOBI, IMHO. I've done ePUB/mobi with over 900 "files," including images; and man, the more XHTML files, the snappier THAT goes.

Hitch
Hitch is offline   Reply With Quote