Quote:
Originally Posted by JSWolf
Here is the compatible ePub. You already have the ePub 3 version so there really isn't any need for as the compatible ePub because it's not really compatible. Have a look at this and see how simple the CSS and code is and how compatible it is. It's not complex and it works with RMSDK. RMSDK is the most widely used software for reading ePub so your eBooks really should work with it.
|
With this ebook you haven't done anything that our compatible epub build doesn't already do. You use CSS class selectors, just like our compatible epub build does. Our compatible build also uses > and + selectors which IIRC were supported on older ADE versions anyway.
However you downgraded to epub 2.0.1--the version of the spec from 2007--while our compatible epub is epub 3.2; you removed all epub:type attributes, which are important for accessibility (screen readers for the visually impaired, and so on); and you stripped almost all metadata. I consider all of those big losses. Besides that, there is no obvious technical difference between the two, unless I missed something. (Which is entirely possible, there are too many differences here for a folder diff to be meaningful.)
I appreciate what you're trying to do, even though I disagree that you've succeeded in demonstrating anything. But you're straining to keep ebooks trapped in an IE6 world. The web, and ereading systems, have moved on.
Arguing in this thread is going to be largely pointless. If you have real technical solutions, I invite you to open a GitHub discussion or even a pull request to implement them yourself. Here is a link to our toolset:
https://github.com/standardebooks/tools