Quote:
Originally Posted by ibu
I suspected, that "page-break: before" is not supported. I agree: the lack of "page-break: avoid" is worth.
Because you emphasized "in KePubs". Does it mean, epubs (which means, it must be an EPUB2) do support "page-break"?
|
Yes the Adobe ePub reader supports page-break-before: always; page-break-after: avoid; page-break-inside: avoid; etc.
(there is no such CSS property as page-break, there is only page-break-before, page-break-after, page-break-inside.)
Quote:
About the performance:
Is that generelly true, even for newer devices like a H2O? I mean, is there really a difference in the performance the user could "feel", or is it only one, which can be measured?
I ask, because I like the idea of "one single content document does it all" very much.
|
It makes a big difference, if you try to put a whole large book into a single html file then you will get a very poor reading experience in the ePub reader with slow page turns, and you might also have problems with the TOC and chapter stats graph features in the KePub reader because these assume that there is one chapter per html file.
This is not just Kobo devices, most ereaders will cope better with an ebook made up of lots of small files than with one large file. Some will even crash or be unable to open the book if the html files are too big.