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.
|
Yes, but if you show an example of one of these large, multi-screen tables, perhaps more specific advice can be given.
Quote:
Originally Posted by Paolo Carnovalin
The only possible loophole is the use of vertical scrolling, which allows the tables not to be truncated; [...]
|
Off the top of my head, I can't think of many (any?) tables that would make sense in a single page, but wouldn't if split across pages.
What can happen though... is accidentally missing your <thead> + <th>. Those two let headers duplicate across screens, helping make the multi-page table be more readable.
Without <thead> + <th>:
Code:
Position FirstName LastName
1
2
3
4
[...page break...]
5
6
7
8
[...page break...]
9
10
vs. With <thead> + <th>:
Code:
Position FirstName LastName
1
2
3
4
[...page break...]
Position FirstName LastName
6
7
8
[...page break...]
Position FirstName LastName
9
10
The 1st type, you might get lost and forget which column is which.
The 2nd type, the column headers follow you across pages.
- - -
Side Note: And if the table doesn't make sense, then I strongly recommend
reading the advice/book I recommended in 2021.
What most likely happened is the original author designed a "table-like graphic".
For more "table design" best practices info, also see some of my comments from a few months ago:
If you squash this problem at the source—and teach them better and clearer ways of representing the original data—you can also help all their future documents as well. (And the readers will thank you too!)