View Single Post
Old 05-14-2024, 02:03 PM   #104
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: 48,719
Karma: 174510110
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by JSWolf View Post
Because it's the software on Kobo and Tolino. Also, it renders overall better then Access on a Kobo. If it was updated, it could do ePub 3 better with the better rendering.
At this time, it appears that the default renderer on Tolino's v5 software is very similar to the WebKit based renderer on a Kobo. Just BTW, the renderer that Kobo originally used for ePub3 was ACCESS (all caps) which was replaced by the WebKit based renderer.

As for RMSDK doing better ePub3? Looking at the latest test results I can find, quite a few of the tests show that neither ADE nor RMSDK are doing all that well. I have to admit that Adobe pushing epubtest.org on their website is a bit of a laugh.

Quote:
Originally Posted by JSWolf View Post
Out of the box with no patches and added config options that a lot of people don't know about, KePub does not look all that good. ePub does look better.
Personally, I prefer RMSDK for it's font handling but very few of the people I know who use ereaders are likely to notice which renderer is being used.
DNSB is online now   Reply With Quote