View Single Post
Old 05-09-2013, 06:53 PM   #30
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: 45,210
Karma: 168808723
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by taming View Post
No, it seems to be caused by non-standard (or at least different than when a publisher does it) embedded fonts. Or non-standard (at least from Kobo's POV) font specifications in user added fonts.

EDIT: I am going to try to say this in a nice way, but I am struggling. Kobo may be an open device, but that does not, to me, mean that anything ending in .epub is guaranteed to work on it.
Considering most sites where CSS code is discussed still have disclaimers such as "this works with IE 8 or higher, Firefox 4+, Safari 5+" on almost every bit of sample code, there are no guarantees that any css is going to work on any given renderer. You learn what works for most devices and what is an invitation to a world of complaints.

Regards,
David
DNSB is offline   Reply With Quote