Thread: BookFab
View Single Post
Old 01-05-2026, 07:44 PM   #6
xyzzy_foo
Zealot
xyzzy_foo ought to be getting tired of karma fortunes by now.xyzzy_foo ought to be getting tired of karma fortunes by now.xyzzy_foo ought to be getting tired of karma fortunes by now.xyzzy_foo ought to be getting tired of karma fortunes by now.xyzzy_foo ought to be getting tired of karma fortunes by now.xyzzy_foo ought to be getting tired of karma fortunes by now.xyzzy_foo ought to be getting tired of karma fortunes by now.xyzzy_foo ought to be getting tired of karma fortunes by now.xyzzy_foo ought to be getting tired of karma fortunes by now.xyzzy_foo ought to be getting tired of karma fortunes by now.xyzzy_foo ought to be getting tired of karma fortunes by now.
 
Posts: 137
Karma: 637454
Join Date: Apr 2025
Location: Chiyoda, Tokyo, Japan
Device: Kindle Oasis (10th Generation), Kobo Sage, BOOX Go 7
Quote:
Originally Posted by xyzzy_foo View Post
There's no question that Rakuten Group's development team is deeply involved with Kobo eReader's EPUB3 renderer. It supports Japanese extremely well and perfectly handles Shueisha's manga EPUBs, which have a unique structure that can't even be opened by calibre's viewer.
Quote:
Originally Posted by DNSB View Post
Misleading? Kobo's renderer (originally the ACCESS NetFront BookReader v1.0 EPUB Edition renderer which ended up being donated to the Readium project and moving on to their current Readium/webkit based version) has excellent ePub3 support for both reflowable and fixed layout ePub3s.

Yes, the RMSDK renderer has very poor ePub3 support since Kobo has not updated that renderer in quite a while. For the most part, the RMSDK renderer is being used to allow support for Adobe ADEPT DRM protected ePubs. OTOH, virtually all the ePub3 ebooks using more advanced features display without issue on the Kobo webkit-based renderer.
Quote:
Originally Posted by DNSB View Post
Basically, RMSDK was not capable of handling this and so Kobo licensed the ACCESS NetFront BookReader v1.0 EPUB Edition for use on their devices/apps. Later ACCESS code was done with the Readium project SDK which resulted in the PUBPLUS™ Reader v2.0 EPUB.

Later versions of the Kobo renderer were based on the Readium/webkit and Readium 2 SDKs.
DNSB knew the detailed technical background. It seems they were using ACCESS's technology.

Last edited by xyzzy_foo; 01-05-2026 at 07:49 PM. Reason: Add another quote
xyzzy_foo is offline   Reply With Quote