Quote:
Originally Posted by KevinH
"figure" and "figcaption" are actually wonderful changes as they semantically tell the accessbility e-reader so much more about the document structure than a generic "div" with a possible child "img" tag and possible following "p" tag for a caption. In addition, many epub3 layout engines already know to avoid page breaks when generating the page with figure and figcaption.
Since this thread should be about epub3 to kindle font losses and not epub2 vs epub3, I will stop there.
|
Kevin:
I, certainly, am
not claiming that ePUB2 is somehow the end-all and be-all or that we require it for accessibility, etc. but the damned reality is that some vendors, for example, to this day, require ePUB2 to pass their intake. It's frustrating as s**t for those of us stuck in the commercial end of bookmaking. I wish that I could just say to the minions, "hey, gang, let's all switch up to ePUB3 and roll with that," when certain vendors--is it still Lulu, I think, amongst others?--
won't accept ePUB3, or are using an ePUBcheck that's
so damned old (yup, looking at you, again, Lulu), you can't get there from here. Those are distinct but
related problems. I'd love to be able to just create ePUB3 with ePUB2 fallback, but it doesn't work that way. In that way, ironically,
it's actually easier to do KDP than "One ePUB to Rule Them All."
For those who are privileged enough to do their own eBooks, or their own company's eBooks,
huzzah.
But not all of us can do that. Yes,
sure, ePUB2 is on its way out--but slowly, slowly catchee monkey and this particular monkey is bloody geriatric
and using a damned walker as it heads for the door.
I love fig and figcaption myself. I wish I could use them with impunity.
That's all I'm saying.
Hitch