Quote:
Originally Posted by Paolo Carnovalin
My problem was not formatting the code, but explaining to my client that when inserting such a large element into an ePub you can never be sure how this element will be seen by the person reading the book. The only possible loophole is the use of vertical scrolling, which allows the tables not to be truncated; with my question I was trying to understand if this possibility was also a "universal" loophole
 |
For what it's worth: for our customers with larger tables, assuming they cann pay for it, of couorse--we put in BOTH. We put in a section at the bck of the book with "HTML tables," which each table in HTML format, so that the text is readable for accessibility and all that, and searchable and an imaged version, in the body of the eBook. We put a link, below the imaged version ("For HTML version, click here" and a link back at the HTML table).
This works quite well. YES, it's extra work and yes, it's extra $$ for the customer, but...most customers with huge tables seem to have the budget or the willingness to go that extra mile.
Hitch