Quote:
Originally Posted by MrSilverstrike
I'm confused. The kepub renderer (based on ~2014 WebKit) is faster, that's what I'm saying and you are saying as well, no? To use it, you need kepub versions of books. If you generate them, either with Calibre or kepubify (both are great), you force your Kobo to use the kepub renderer, which is generally faster, especially on older devices. Aren't we agreeing?
|
On my Kobo Sage, I find that page turns are not noticeably faster using kepub instead of epub. RMSDK still has better typesetting than the Kobo renderer.
I have also checked speed going back though my Kobo collection to my Kobo Touch and, for me, there is no real difference with newer firmware. Sadly my Kobo and Kobo WiFi do not support kepub so no chance of testing there.
Quote:
Originally Posted by MrSilverstrike
Anyway, my point is: if possible, I think most people just benefit from using kepub files. It's just a plain better experience. You get chapter forecasts, faster page turns, etc. and with my upcoming mod (or modified fonts) the somewhat broken text rendering is also improved, almost on-par with KOReader in terms of fidelity, given that the pure outlines are rendered without grid-snapping, which is what the KOReader renderer does, too.
|
For me, the main benefit of using kepub is the support for much more of the ePub3 spec plus oddments such as being able to accept using margin: auto,auto; to center a block.
The reading statistics are of little interest to me, with the forecasts being a source of humour more than anything else. The current book I'm reading is ~148K words and I am about 67% finished. The time already spent reading is 1.6 hours (94 minutes from my calibre statistics) minutes and ~4 hours to finish the book. So I've read ⅔ of the book and it will take me ~2.5 times longer to finish the last ⅓.