Quote:
Originally Posted by rsuchwani
Hitch,
I'm grateful that you've taken out time to respond to my question from early on and provided me with the years worth of insights, but so far only MicroDrie has 'actually' thought of finding the solution to remedy my issue.
And may be the current suggested solution only work on 'apps' not on 'actual' devices but I only have access to those mentioned apps/device so my test ranges to only those.
But since you have access to almost all the devices given that you run the eBook conversion company, will you be able to actually test the ePub on devices and find out whether the solution works or not?
|
Yes, MicroDrie mucked around and found a "solution" that works--on browsers and software readers. The reason that the rest of the schmucks here didn't even try it is because we
KNOW that tables are murky at best, in ebook readers and that when they carry over multiple screens, as yours do, you are courting Mephistopheles. And here's the real kick in the ass--even if they work when sideloaded, you just can't be sure what the processing might do, once the book is live. (To wit, the problem of using embedded spans, on Nooks. Worked fine when sideloaded and puked and kablooie'd in the real, post-processing devices.)
You surely know
exactly what you're asking; sideloading this to every device in my stable would not be quick.
Perhaps some of the other denizens of the deep here might step up, with their hard devices, too, and spare me some aggro? Since I have not one but TWO employees sidelined by Ida?
And lastly--customer and client education is part of what we are required to do. SOMETIMES, you just have to tell a client that what they want is NOT DOABLE or that if you do, the fix may be worse than the illness. This, imho, is one of those times.
Hitch