Thread: Kindle only
View Single Post
Old 08-17-2011, 07:23 PM   #59
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 79,125
Karma: 144284184
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by Elfwreck View Post
If you've formatted your books correctly, using the SW style guide, they should be fine.

Some ereaders have trouble with SW ePubs, because even if you follow the guide exactly, the Meatgrinder doesn't make great ePubs; the coding choices are limited and problematic for some ePub-reading software. However, if it follows the guide and doesn't have complex parts, it'll be fine for normal reading. A book carefully designed could be better--SW doesn't support drop caps, for example, nor even simple tables--but that's not going to matter to most readers.

(Hey, you could set up a sig with a link to your books at Amazon & SW.)
Actually, part of the problem is that in the ePub CSS is redundant code that breaks things. Like font-family for tines new roman or other font families/styles, color codes that prevent changing color, and other things. And to go into the ePub to fix this is not all that easy for a lot of people also, sometimes there isn't a proper ToC for the ePub as the proper ToC is external, not internal.
JSWolf is online now   Reply With Quote