Quote:
Originally Posted by gaphic2
Yes, it has to with long paragraphs, and as Charleski pointed out the widow and orphan control in the page rendering.
But why would the device need to add a page break halfway through a page when there is no issue with orphans/widows, as in the sample epub posted earlier?
|
My best guess is that there's some sort of obscure overflow error which is causing the layout algorithm to give up and just chop the paragraph. In some cases with multiple long paragraphs there can be problems with cascade effects, but this clearly isn't the case here.
Personally, I don't mind widows and orphans nearly as much as seeing the last line of text jump around. It's really a matter of style in the majority of cases. A stylistic source like Bringhurst is of the opinion that while widows (a single line at the top of a page) should be avoided, orphans are acceptable (Bringhurst explains this using some typically flowery reasoning
). So you could try widows: 2; orphans: 1;.