So I feel we've come to the spot where there's standards, but then there's convention over (a) decade(s) that just trumps standards. Reminds me of DHCP where I've yet to come across three implementations that agree on certain aspects. Also, is 'supports epub x.y' been a selling point in any reader so far?
I'm looking through the changes and holy hell, this makes me feel like punching an engineer, and I am one! Everything is buried under three or more layers, requiring at least 3 clicks and a bunch of scrolling and usually just refers to what they've changed compared to the PREVIOUS version. While fine for a standard, this is absolutely awful for anyone who doesn't work with epub files daily (which I'm guessing is a very small minority).
If you're interested in changes written for humans, this link is what you're looking for: https://www.w3.org/publishing/epub32/epub-overview.html It doesn't contain motivation for these changes, though, so we'll go with "some engineer thought these would be a good idea"
I guess I'd like to ask the working group:
#1 How widespread would you consider high/recent version support for epubs to be?
#2 How would you sell epub 3.2 support to people developing e-readers or reader applications?
#3 Why isn't the first page filled with "Hey guv, you're an engineer who's interested, here's what epub is and does, and here's a link with all the recent changes along with update motivation information" because looking at this site, I could not find a single thing for convincing manager/C-level types to grant 200 product update hours for this.
Me too, and I wish SVG support was better on most eReader (not a good experience so far), and that there was official support for MathML or something equivalent. It hurts to see so many books using raster pictures to display a formula or a diagram, when it would look crisper and flow better if it was vector-based.
You'd think there would not be such a great difficulty in this, since epubs are constructed out of the same basic tech stack as web pages.
I think the fundamental problem is that Amazon, Apple, etc., don't have much incentive to support texts beyond the most commercial genres.
I found a German text from 2018 that covers EPUB 3.0-3.2 (which was obviously still a draft back then): https://www.dpc-consulting.org/epub-3-3-0-1-3-1-3-2-das-vers...
It links to a long blog post that covers recent EPUB development by Dave Cramer, co-chair of the W3C Community Group: http://epubsecrets.com/why-specs-change-epub-3-2-and-the-evo...
EPUBCheck is an open source tool that can check your EPUB files against the EPUB 3.2 spec. https://github.com/w3c/epubcheck
There's no point using a feature if it'll just break the book for the vast majority of your audience, and it doesn't look like that situation is going to change anytime soon.
Amazon in the US at least has sewn up the ebook market such that they have no interest at least in implementing open standards. The best thing to do in these situations is to vote with your wallet.
Kind of sad XULRunner got killed or I could run EpubReader as a stand alone app.
I searched high and low for a copy, and even emailed the developer. Their response made me quite sad: "I'm afraid that I don't know that I even have a build at this point."
Who knows if it would even work on modern macOS, but I bet it would, as long as it was 64 bit. macOS's backwards compatibility is better than some seem to imagine.