View Single Post
Old 08-08-2017, 11:10 PM   #23
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: 47,216
Karma: 171291588
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Hitch View Post
Oh, and the widows/orphans thing, in eBooks--in about 50-70% of them, it doesn't work. If you're on iOS, fine (or Kobo, b/c they've mooched a lot of the iOS rendering engine, which in turn had originally moooched ADE...), or Readium or Azardi, but after that, rotsa ruck.
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.
DNSB is offline   Reply With Quote