View Single Post
Old 05-26-2024, 02:57 PM   #13
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: 80,060
Karma: 147977995
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 DNSB View Post
For what it's worth the WebKit based renderer used by Kobo for .kepub.epub is based on Readium. Back in the distant past, Kobo used the ACCESS NetFront™ BookReader EPUB Edition engine to render ePub3 files. After ACCESS contributed to Readium development by supplying its NetFront™ BookReader EPUB Edition engine to the Readium project, Kobo switched to using a customized Readium renderer.
Given that Kobo switched to a customized Readium, why didn't Kobo fix the rendering problems with KePub? It renders are badly as it did before the switch.
JSWolf is online now   Reply With Quote