Quote:
Originally Posted by jhowell
What I mean is that the latest KFX renderer seems to treat headings as if they have page-break-inside:avoid and page-break-after:avoid set.
If you try to change that behavior by setting page-break-inside:auto or page-break-after:auto, nothing changes. In fact those property settings will be stripped out during conversion to KFX.
The only way I have found to disable this handling is setting widows:1 and orhpans:1 on the heading. That seems to disable the default handling.
(I hope that was clearer.)
|
Yes, much, many thanks.
Quote:
|
Are you reading on an e-ink Kindle device using the latest (5.12.2) firmware? That firmware is broken in that it always avoids widows and orphans even if the book is coded to allow them.
|
To quote Popeye, I yam, I yam indeed. It's driving me bats**t.
Quote:
|
The iOS, Android, and Fire apps honor the coding of the widows/orphans properties, so I expect that the next e-ink Kindle firmware release will fix this.
|
Your lips, God's ears, all that.
Quote:
|
I think Amazon made a poor choice in changing Enhanced Typesetting to avoid widows and orphans by default. I suspect that some publishers will be updating their books to add widows:1 and orphans:1 for regular paragraphs to work around this change.
|
-----
Quote:
|
Related to this topic, the page-break-inside:avoid property is usually stripped out during conversion to KFX. However I have found that it is usually carried through and functions as expected if it is used in conjunction with float. If you open the attached EPUB with the latest Kindle Previewer and try different font sizes you will see that it does not want to split up the text in red.
|
Hmmmm....I'll go play with that.
Thx,
Hitch