Quote:
Originally Posted by Jellby
In order to render two files without a pagebreak, the reader should be able to process two files (or more, as there could be many files fitting in a single page) simultaneously and display them on the same screen. I'm sure that's not impossible, but I'd say it's not trivial and I don't think that'll happen in the near future.
Given that Adobe-based readers still add spurious pagebreaks in the middle of long paragraphs (and in the middle of the screen), attempting to create a "continuous" text seems rather futile anyway.
What could change is this:
There's no fundamental limit in what ePub can handle. With enough memory, and a reader that does not add its own limitations, you could have HTML files as long as you want.
|
Well, yes, Jellby,
Technically, that's true, but in practice, we all know that huge ePUB files will choke most ePUB readers at some point. I've had large ePUBS with many chapters (files) in them that nearly killed a NookColor. So...I wouldn't recommend trying it.
weberr:
What could a few breaks, that are nearly transparent, going to do that would "destroy the objective of the file," really, given that it's a book? (I mean...it's a book, not a program or an app. Even then...) As has been mentioned already in this thread, ADE, which drives a large number of readers, will arbitrarily insert page breaks in paragraphs hither and yon, anyway--so even if you do only create a single HTML-file ePUB, you have a better than 90% probability that your readers will experience page breaks along the way.
So: I'm really curious. How could a few page breaks destroy the file's "objective?" This is such unique wording that I'd love to know.
Hitch