Quote:
Originally Posted by acabal
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 |
The reason to do what I did is maximum comparability with the most software. You have the advanced version which has all of what I removed. The problem is that the compatible version isn't very compatible.But my changes make it much more compatible. So you would have the best of both worlds. You would have a version that most can read and you'd have a version that's your ePub 3.2 advanced version.
The problem as I see it is that sure, you are using the ePub 3.2 spec, but most software for reading ePub barely handles ePub 3.0 let alone ePub 3.2. So because of this, you are doing a lot of work that a lot of people won't be able to read because it won't work or it won't look good.