Well, this is strange, I know I replied to this already, but that reply seems to have disappeared! Or maybe I neglected to hit the submit button and closed my browser or something -- but that would be odd.
Anyway, I'll try to replicate my earlier reply...
Quote:
Originally Posted by GrannyGrump
I think it was your thread https://www.mobileread.com/forums/sho...-before&page=2
Look at posts 30 thru 33. The space was intended to force ADE to jump the "page number" up to the next digit.
I don't know that that is such a critical issue, depends on which you consider worse: A page number repeated, or the top of page mis-aligned. |
That's the first I've ever heard of a device getting the page numbering off (for any reason). Seems odd that that would happen.
In any case, the reason for adding in the nbsp into that div would appear to be from this comment from Jellby...
https://www.mobileread.com/forums/sho...9&postcount=32
...where he said that "For some renderers you may have to include some content in the <div>, or it will be discarded," and then putting that nbsp in there for "content." Looking at my original code, I'm surprised that just that nbsp did bump things down at all anyway, since my margins, padding and line-height were all set to "0" -- it's as though
that was all ignored.
Quote:
|
You could always just split the file at each new page-break, and have multiple small files.
|
Except that goes back to the reason for that whole other thread -- having separate files causes ADE to insert blank pages where you don't (or may not) want them.
Also, from Turtle...
Quote:
Originally Posted by Turtle91
It makes it so much easier to navigate within Sigil, search/replace is much faster on smaller files, and it guarantees the start at the top of a new page. AFAIK there are some devices that don't always honor <page-break> as they should.
|
I agree on the navigating-within-Sigil advantage, for sure, although I guess my concern is the aforementioned blank pages in ADE issue. As for how fast search & replaces are, well, they just take a second or two for me on my computer as it is now, so cutting that in half isn't really much of an advantage.
I was really only planning on putting this book on the iBooks store anyway, perhaps I shouldn't be too concerned about whether the page breaks work (or not) in other devices -- although it's certainly nice if they do, if I ever change my mind about that. The issue over ADE inserting blank pages (as per that other thread) does bug me, though, if I were to go with separate files.