View Single Post
Old 08-20-2024, 07:08 PM   #9
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: 46,864
Karma: 169716272
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Sirtel View Post
Personally, I can't stand the gaps widows/orphans management often leaves at the bottom of the page in epubs. So I always change widows/orphans to 1 in all my books, and also in the config file of my Kobos.
My stock body class has widows: 1; and orphans: 1;. I also use the RMSDK Disable orphans/widows avoidance patch. I do remember years back someone mentioned using readingWidows=0 and readingOrphans=0 (or was it =1??) in the Kobo eReader.conf file but in my testing at that time, I did not find those settings having any effect. I did find that settings widows and orphans to 0 in the CSS had two different effects. Some renderers treated 0 as equivalent to 1 and others disregarded it and went with their default of 2 or 3.
DNSB is offline   Reply With Quote