Quote:
Originally Posted by silkpag
http://toc.oreilly.com/2008/04/keep-...play-nice.html
Now, with your programmers so busy chatting up folks on blogs, there might be a few weaknesses in the software itself. But that's OK, as despite the fact that, you know, in the age of $5 1 GB SD cards, Adobe's software chokes on a couple hundred K of text, we're told that it's "best practices" to chop every book up (even classics like Moll Flanders or Tropic of Cancer that don't have chapter breaks):
http://blogs.adobe.com/digitaleditio...igital_ed.html
The above site is perhaps my favorite little bit of deception, as of course this failing of Adobe's makes all other means of creating .epub files (the DAISY Pipeline, Mischa's OEB2Epub, whatever Bookglutton's running) untrustworthy... but of course that's the fault of the user, not Adobe.
|
Peter explained why multi-flows are necessary months ago (on this forum too). That's the reason why I switched the ePub output from Feedbooks to multi-flow. Aside from Adobe or Feedbooks, anyone else could do the same as long as they use elements that indicate the subdivision of a book, or use some page-break CSS properties. It only took me a day or two to change this on Feedbooks.
But I agree: for some books it's almost impossible to divide them into multiple flows. For example, open a book from Proust: you won't find a single page break and they're barely divided into 2 or 3 parts.