View Single Post
Old 05-09-2013, 06:49 PM   #29
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: 47,260
Karma: 171291590
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by guma View Post
At least around here KOBO readers are advertised as 'open' devices. Thus side-loading books from other sources than KOBO should not be considered some sort of hack which they can simply ignore but is a standard use case. As far as I can see, the font display problems mentioned here are not caused by bad epub code anyway.
Some issues are caused by embedded fonts, some are caused by sideloaded fonts but the majority (in my opinion) are caused by css style code that is poorly written. Some of those code issues are caused by the differences between the renderers used on various devices -- it works on a Sony but not on a Nook or a Kobo type of problem. Kobo suffers here because they are supporting two renderers. The Adobe Reader Mobile seems to be close factory stock as most of the issues that show up using ADE on my computer are also issues on my Kobo reader. As to the state of the ACCESS NetFront BookReader, I haven't seen it elsewhere so it's hard to comment on just what changes other than adding the DRM code have been made by/for Kobo.

Regards,
David
DNSB is offline   Reply With Quote