Quote:
Originally Posted by DNSB
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.
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.
|
Does the webkit based renderer on Kobo suffer from the same issues as the Shine 5's default renderer?
The letter spacing is way too narrow:
https://www.mobileread.com/forums/sh...28#post4471428
I only use RMSDK because I find it makes texts much easier to read with its wider letter spacing.
Also, font weight adjustment, embedded fonts, page breaks, orphans and widows don't work in the default renderer. I often have to switch between fonts a couple of times before sideloaded fonts work. Switching between text alignment settings can be tricky as well: Sometimes I have to close and re-open the book to see the effect. And the last couple of lines of a chapter sometimes get lost.
Quote:
Originally Posted by user105
which is funny because i am still set to rmsdk as epub engine and cannot switch back. i am worried to factory reset this device because without switching engines, i cannot open books in an acceptable way.
|
You're still on RMSDK because it's set in the Kobo eReader.conf file.
Change "EpubSideloadedRenderer=RMSDK" to "EpubSideloadedRenderer=default" to go back to the default renderer.