Quote:
Originally Posted by DNSB
Kobo uses Adobe's RMSDK for rendering epub2 ebooks so hard to say they've mooched the iOS rendering engine. For epub3 (.kepub.epub or .fxl.kepub.epub), they use the ACCESS NetFront™ BookReader EPUB Edition which is based on WebKit though some claims are that it was originally developed using the KHTML/KJS libraries from KDE which are ancestral to WebKit.
For what it's worth, the RMSDK renderer respects widows/orphans with a default of 2/2 if not overwritten in the CSS while the ACCESS renderer disregards them (equivalent to setting both to 1) so if you are seeing widows/orphans affecting the display on a Kobo ereader, you're using RMSDK.
|
No, actually, I was talking about the fact that the same FXL coding that works on iBooks will function pretty much perfectly on KOBO. With regard to their internal rendering, trying to get kepub to behave is a whole other story. :-)
If they haven't mooched some of the rendering settings, etc., from iBooks, the whole FXL thing is fairly remarkable. And truly--didn't mean to discuss iBooks; I was talking about the relative uselessness of the w/o settings.
Hitch