View Single Post
Old 12-19-2019, 01:39 AM   #12
Tex2002ans
Wizard
Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.
 
Posts: 2,306
Karma: 13057279
Join Date: Jul 2012
Device: Kobo Forma, Nook
Quote:
Originally Posted by 1v4n0 View Post
Hello, what do you think is the best way to render tables on epub/azw3 ebooks? I usually turn them into html tables,
Yes, that's your best bet. It will:
  • Follow all user preferences
  • Be readable by Text-to-Speech
  • Copy/Pastable
  • Searchable
  • [...]

But because of very huge font sizes + skinny devices (cell phones), you should minimize how many columns across your tables are (~5+ columns is about the soft limit, depending on data).

You may have to display your data in a very different way:

1. "Transposing" or "verticalizing" the tables:

Change a wide 3x13 table and flipping it to a tall 13x3.

See example I posted in 2013, where I also went into more detail on HTML tables: "Tables in an EPUB?".

2. Converting from a table into actual text:

For example, this table:

Code:
------------------------------
First   |   Last  |  Votes
------------------------------
A1      |   A2    |   A3
B1      |   B2    |   B3
------------------------------
could be converted to text as:

Spoiler:


Code:
First: A1
Last: A2
Votes: A3

First: B1
Last: B2
Votes: B3


3. Split into X amount of skinnier tables:

Spoiler:
Code:
-------------------
First   |   A1    |
-------------------
Last    |   A2    |
-------------------
Votes   |   A3    |
-------------------

-------------------
First   |   B1    |
-------------------
Last    |   B2    |
-------------------
Votes   |   B3    |
-------------------


Quote:
Originally Posted by 1v4n0 View Post
I guess turning them into images would make them more cross-compatible, but it would also make the books heavier.
Images of tables can't be spoken via Text-to-Speech. And depending on the resolution of your images, they may not age well at all. (With higher DPI/resolution devices, some of those old tables-as-images became ant-sized.)

If you want to read more of the pros/cons of all different methods of displaying tables, there's also the discussion in "How to Control Fonts in SVG Images of Charts and Tables?".

Quote:
Originally Posted by Turtle91 View Post
image "weight" can be minimized by choosing the correct format (.gif, .png, .jpg).
And if you do have to save the table as an image... use PNG (Indexed if you want really small filesize).

Do not use that crappy JPG. :P
Tex2002ans is offline   Reply With Quote