View Single Post
Old 04-20-2018, 07:14 PM   #8
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,369
Karma: 169098492
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by MartinM View Post
Thank you for the replies.
So, without getting into CSS and HTML coding, which I have no experience with, if my epub and mobi files look OK in ADE, Kindle, Kindle Previewer, Ice Cream, Readium, Edge, Kobo, UB Reader then I should not worry about a picture not being centred in Nook, Prestigia, Aldiko or Bookviser?
Pretty much yes. Quite a few ereader apps take a very haphazard approach to implementing the epub standard or simply use their own internal CSS. Not much you can do about those. For me ADE/RMSDK (it's embedded cousin), Readium and ACESS Netfront (Kobo licenses this for rendering epub3 files) are the ones I worry about. Generally, an epub that looks good on ADE will look pretty decent when converted to a Kindle AZW3.
DNSB is offline   Reply With Quote