View Single Post
Old 11-04-2017, 12:15 AM   #5
slowsmile
Witchman
slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.
 
Posts: 522
Karma: 788808
Join Date: May 2013
Location: Philippines
Device: Android S5
@JSWolf...Generally, displaying tables as gif or jpg images is the way most people do it in epubs. I've also done it in some of my generic epubs quite successfully. But there are certain rules that you must follow when you format tables as images. For instance Kindle image compression will make all image lines and fonts thinner. To avoid this problem of "stringy" or thin image fonts all you have to do is either use a thicker font like arial or just make the font bold. And I've never had a problem sizing fonts for image displays. This really shouldn't be a problem if you test it properly and adjust font size appropriately. And whenever I have created tables in ebooks I always usually use cell fonts that are slightly bigger than the body text anyway. This makes the table easier to read on smaller devices and also helps to reduce font "stringiness" issues.

Last edited by slowsmile; 11-04-2017 at 07:49 AM.
slowsmile is offline   Reply With Quote