Books that wouldn't work very well as audio books usually won't work well as ePub either. Charts, maps, complex typography, etc., that would be lost in audio form is mostly lost by ePub. I don't know how much of that loss is due to to ePub format, how much due to ePub viewer apps, how much due to ePub creation tools, and how much due to creators just not trying very hard, but the combination makes most high-quality textbooks much better as PDF, which "beach literature" is better as ePub.
Fun epub file trick: rename the file .zip, unzip -a yourbook.zip (double click unzip doesn't work on osx for me for some reason) and check out the html, css, images and xml of your book.
[1] https://en.wikipedia.org/wiki/EPUB [2] https://www.w3.org/TR/2005/WD-xhtml2-20050527/elements.html
IMO, ePub readers have the best justification algorithm: flush left, and the best hyphenation algorithm: never hyphenate. PDFs often force full justification on you, which makes it harder to read because all the line endings have the same spacing, making it easy to lose your position in the text.
But I think there's a synthesis possible between what you mean and what OP meant: ePub readers are somewhat better at adjusting to the reader. "Reader" here in terms of both the device and the actual human. Text can reflow, columns are used only where they make sense, and settings can be changed.
PDFs are better at allowing the creator to, well, create. I know there's a hard core demographic that doesn't believe in any sort visual design. Yet there are topics and authors where choices of placement, font, color etc. are made with intent, and to good effect. Everything Tufte comes to mind.
It should be possible, with something like Apple's Book Author, to create such designs that work well within the e-Book format. But I haven't seen any examples, probably because I rarely read textbooks these days and tend to buy paper copies of such books, anyway.
In as far as I have seen illustrations in non-PDF formats, the results are dismal, with all sorts of sizing problems etc.
I don't have that problem. I find find ragged-right with no hyphenation less pleasant to read and to look at. When I'm reading a novel on my Kindle, I have it set ragged-right because the Kindle doesn't justify well (just word spacing I think). Same on the web. But when I can get good justification and hyphenation, like on a properly typeset PDF or physical book, I prefer it.
This isn’t anything to do with PDF, of course; it’s just representing the baked result of a text rendering process. Your device could do that rendering itself just fine; it’d just take a while (much longer than it takes to change font family/font size and see the result in your favourite eBook reader.)
It’d be interesting to see an ePub-like standard that kept the text as semantic text, and rendered “at runtime”, but not “in realtime”; rather using a set of render preferences you set up before-hand to render the book once when you first download/sync it. Sort of like how runtimes like .NET dynamically recompile downloaded bytecode to native code to “specialize” the code for the device they’re running on. With such an approach, you could rely on a render-model that actually spens time doing good, constraint-based rendering of the text to avoid rivers/widows/orphans/excessive hyphens/etc.
You could get pretty far in cutting down the perceived time of this render by just splitting each work into chapters and rendering a chapter at a time. You would be able to start reading once the first chapter finished rendering. Which, for most normal types of books, on the sort of CPU an eBook-reader has, would “only” take ~10 seconds.
https://github.com/jaroslov/knuth-plass-thoughts/blob/master...
It’s always fascinating how these older algorithms and research is still highly relevant and it’s implementation being debated over.
I am also sensitive to bad typography and sadly most ePub readers fail miserably at this. I don't want a "blob of text" with random font sizes.
When it comes to preserving the intended layout, PDF simply translates better.
I actually did this for a paper or two, and turns out long math expressions break things, but otherwise not too bad.
I wouldn't mind small page pdfs also being release as well as the large ones.
I've yet to see a programming book in epub/mobi format that is even reasonably readable
> As a semantic language, DocBook enables its users to create document content in a presentation-neutral form that captures the logical structure of the content; that content can then be published in a variety of formats, including HTML, XHTML, EPUB, PDF, man pages, Web help[2] and HTML Help, without requiring users to make any changes to the source. In other words, when a document is written in DocBook format it becomes easily portable into other formats. It solves the problem of reformatting by writing it once using XML tags.
I've never understood how to compile to a target format, though.