Quote:
Originally Posted by Hitch
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
|
And don't forget software that doesn't understand ePub 3. Kobo won't display the sample ePub 3 properly because the version of RMSDK used is too old. And Kobo devices are not old. So you cannot say to forget old devices because not all new devices will work. And there are ways to deal with the ePub 3 so it works as ePub 3 with ePub 2 fallback.
Have a look at Android and how many "supposed" ePub readers won't work properly with this demo ePub.
In this demo, just do this...
<figure>
<div class="someclass">
In the CSS, there's no need for rem. use em. Forget hv and use % with height and width.