View Single Post
Old 04-14-2020, 03:00 PM   #5
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,665
Karma: 169712392
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by stumped View Post
Good point. Remove widows and orphans is the opposite of "make all screens have the same number of text lines". The setting for achieving the latter is "allow widows and orphans"? Unless I have double negatived myself into a confused mess (which is a possibility )

I set W and O values to 1 in css ( having been lectured about not setting them to zero) and all my pages render full length. Is that = removing them?
Setting widows and orphans to 1 is the logical equivalent of removing them. If there are no widows/orphans defined, RMSDK defaults to 2. To keep things simpler, I set this in the body css instead of having it in multiple locations. However this will not guarantee the same number of text lines on each page since chapter headings, section breaks, spacing between paragraphs can all cause a gap at the bottom of a page where a line will not fit.

I prefer that possible gap to having a page that is solid text with no extra spacing between elements.
DNSB is offline   Reply With Quote