View Single Post
Old 01-24-2023, 07:09 AM   #31
Quoth
Still reading
Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.
 
Quoth's Avatar
 
Posts: 14,447
Karma: 107078855
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper
Quote:
Originally Posted by DuckieTigger View Post
Forcing a page break is not the problem if you always want a page break. The issue is similiar to ignoring orphan setting, only because you underline the first word, and then it thinks it is ok to ignore orphans that are smaller then your specified minimum.
But forcing the avoidance of a break is nearly impossible. That always implies a random earlier forced break (due to screen size, dpi, font size etc). Only some renderers can calculate it, so it's only going to ever work on some devices and apps.

I think also some people don't understand widows and orphan settings either, like why in Western languages they are by default 2 and why 0 is meaningless, but 1 means don't do processing to avoid widows and orphans. Widows or Orphans at more than 1 is indeed related to "don't break inside" but easier for a renderer to process. Only terrible apps ignore Widow or Orphan settings.
Quoth is offline   Reply With Quote