View Single Post
Old 05-09-2013, 07:36 PM   #31
guma
Connoisseur
guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.guma ought to be getting tired of karma fortunes by now.
 
Posts: 93
Karma: 473808
Join Date: Jul 2012
Device: kobo touch
Quote:
Originally Posted by DNSB View Post
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.
Fair enough. But as far as I remember - correct me if I'm wrong here - these issues with 'incorrect' (or, to put it neutrally, 'undesired') font display appeared only a few firmware versions ago. Before that everything was fine in that regard. Thus there already is/was a solution for a more robust epub rendering that is not so heavily affected by variations in epub css code.

As for having to support two epub rendering engines in one firmware I can see that this requires some additional effort on KOBO's side ... on the other hand nobody forces them to do that and it is no excuse for bad or sub-par performance of either of these rendering engines.
guma is offline   Reply With Quote