Quote:
Originally Posted by KevinH
New files by default are always treated like a hard page break. If you do not want a hard break, is there any reason not to merge these two files into one? Sigil can typically handle the merge easily.
Browsers are typically file based, and most e-readers are browser based today. Maybe someone else knows of a trick either using css or javascript that might work, but I have never seen that used in a commercial epub before.
|
My question is strictly motivated in the spirit of backwards compatability for older e-readers that had a hard 300KB limit on file sizes within an epub, or even newer readers whose RAM is sufficiently limited that single file ebooks can slow down rendering.
What I'm trying to figure out is if i can accomodate that 300KB limit while preserving narrative flow (by breaking the html file and applying some super-secret CSS that overrides the reader's inclination to treat the end of a file as a hard pagebreak). But it looks like you and
@Jellby are pretty confident that's a no-go. And as I'm reading on KOReader, I'm think I'm going to take Jellby's comment as license to throw caution to the wind and move ahead with these 4-5,000 line html files.