Quote:
Originally Posted by Hitch
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
|
Hitch -- purely personal choice and a peculiarly strong offense at less than perfection. If the author, including myself, for his own reasons, felt it essential to his flow of story to make and print it as one long and continuous paragraph, then I just naturally want to duplicate that objective in an ebook form. Yes, I could use Sigil and edit the individual files to my satisfaction and then make it one giant html file at the end -- which probably will choke some readers. But, what's the big deal about not including such a command in the spec and ebook readers being designed to act properly on such a command. After all, judging by the traffic on this one thread/subject over so many years, a lot of us want that capability. After all, its all just software.