Quote:
Originally Posted by Hitch
Oh, man, I feel ya. I cannot tell you how many times some yutz (or yutzette; Yutzes are EEO positions) will get "sly" with me, after we've delivered their ePUB, (or pre-sale) interrogating me to be SURE that yeah, bygod, that we're going to give them an ePUB3 ePUB, not some old lame ePUB2 ePUB. (sigh). Whereupon I always ask them what vendors they think they're going to distribute to, given that some STILL do not support ePUB3, and or course, many devices are not ePUB3-friendly or even viable. But, man, some other bozo someplace on the Net--someone with zero credentials, other than a screen name and nothing else--said that they MUST have an ePUB3. (ughghghghghghghgh).
Don't forget that Apple created iBooks, using the ADE engine, for the iOS devices. It's only relatively recently that it was adapted and renamed for the desktops/laptops. K4PC/Mac doesn't work the same as a Fire tablet, either, so...just explain it simply--different devices, different capabilities. Like the difference between a TV with PIP, and one without. Both TVs; both will show you shows, but the HOW of how they show you shows, well...that's technological progress, right?
Hitch
|
I blame Amazon and iTunes for the problems. I mean of course a customer is going to do a search for epub3 specs, find something cool they want to implement and then have a reasonable expectation that they can get what they want.
And yes--the answer we have to give these folks is different apps and devices, different code rendering. But honestly that's just covering for Amazon and iTunes. We're not talking about insanely difficult implementations here. Ebook code is after all still very simplistic. Shouldn't be hard for these companies to issue fixes for these problems. Same with Amazon. How hard would it be to make embedding fonts a painless process? Apparently pretty hard. But if they did make it simple, wouldn't they get much better products on their store and better reviews and more sales? I do realize it is too much to ask though
