11-12-2019, 05:00 PM | #16 |
Wizard
Posts: 1,539
Karma: 6613969
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
|
Well, there is not much to say; with Kindle Previewer 3.35 the property page-break-after: avoid and page-break-before: avoid is availaible. If you use the Kindle app for android you'll need the last version. And I tested .KFX ebooks made with the last version of your plugin and the properties are being perfectly supported. Very usefull for captions and to avoid lone <h*> tags at the end of a page.
EDIT: However it seems to have a restriction: you can't have two consecutive tags (i.e. <h3> followed by <h4>) with those properties. Last edited by RbnJrg; 11-12-2019 at 05:51 PM. |
11-12-2019, 08:56 PM | #17 |
Grand Sorcerer
Posts: 6,494
Karma: 84420419
Join Date: Nov 2011
Location: Tampa Bay, Florida
Device: Kindles
|
If you have an example that behaves differently when the page-break CSS is included or omitted I would like to see it. In my testing there has been no difference in the KFX output produced whether or not those properties are used.
|
Advert | |
|
11-13-2019, 07:18 AM | #18 |
Wizard
Posts: 1,539
Karma: 6613969
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
|
Now <h*> tags are employing BY DEFAULT the properties "page-break-after: avoid" and "page-break-inside: avoid". You won't be able to see any <h*> tags lonely at the end of a page inside a .KFX book made with KP 3.35. Even <h*> tags with multiple lines (with or without <br/> present) will be displayed together in the following page. That didn't happen before.
|
11-13-2019, 09:18 AM | #19 | |
Grand Sorcerer
Posts: 6,494
Karma: 84420419
Join Date: Nov 2011
Location: Tampa Bay, Florida
Device: Kindles
|
Quote:
Added: Actually, there does appear to be a way that publishers can have a little control over this. In my testing setting widows/orphans on a heading disables the behavior of preventing a page break between it and the following text. I don't know if Amazon intended for this to happen, since none of this is documented. Last edited by jhowell; 11-13-2019 at 09:51 AM. Reason: Add more info |
|
11-13-2019, 10:57 AM | #20 | |
Bookmaker & Cat Slave
Posts: 11,459
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
Speaking of, I'm reading a Holmesian Pastiche that was published some years back and I know the formatter for Titan Books, so I know for a fact it wasn't KFX; it was a MOBI / ePUB file, and this thing with the goddamned W/O is starting to make my teeth grind on almost EVERY DAMNED PAGE. Hitch |
|
Advert | |
|
11-13-2019, 11:35 AM | #21 | |
Wizard
Posts: 1,539
Karma: 6613969
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
|
Quote:
Code:
<h6><img class="whatever" alt="" src=".../Images/YourImage.jpg" /><br/><span class="caption">This is a caption</span></h6> I'm doing further test to know the scope of what can be done. So far, even in epub3, the property "page-break-inside: avoid" is unsupported, but with the new KP, <h*> tags with multiple lines are showed together. So maybe we can use something like: Code:
<h6 class="poetry">Blah, blah, blah,<br/> blah, blah, blah,<br/> Blah, blah, blah,<br/> Blah, blah, blah.</h6> And indeed, nothing of that is documented and I think Amazon will polish all this stuff in next versions of KP. |
|
11-13-2019, 11:43 AM | #22 | |
Wizard
Posts: 1,539
Karma: 6613969
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
|
Quote:
Code:
h1, h2, h3, h4, h5, h6 { orphans: 1; widows: 1; } |
|
11-13-2019, 12:44 PM | #23 | ||
Wizard
Posts: 2,297
Karma: 12126329
Join Date: Jul 2012
Device: Kobo Forma, Nook
|
Quote:
So according to what is being said, code such as this still won't stick together? Code:
<div class="poem"> <p class="poetry">This is a poem.</p> <p class="poetry">This is a poem.</p> <p class="poetry">And this is a poem.</p> </div> Code:
div.poem { page-break-inside: avoid; } Quote:
Code:
p { orphans: 1; widows: 1; } (This has been something that has been frustrating me in my Kobo Forma EPUB renderer. I was complaining to JSWolf about it a few months back. KEPUBs render with default 1 widows/orphans, but EPUB renderer idiotically defaults 2.) Last edited by Tex2002ans; 11-13-2019 at 12:47 PM. |
||
11-13-2019, 01:56 PM | #24 | ||
Grand Sorcerer
Posts: 6,494
Karma: 84420419
Join Date: Nov 2011
Location: Tampa Bay, Florida
Device: Kindles
|
Quote:
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.) 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. 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. ----- 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. |
||
11-13-2019, 02:32 PM | #25 | |||||
Bookmaker & Cat Slave
Posts: 11,459
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
Quote:
Quote:
Quote:
----- Quote:
Thx, Hitch |
|||||
11-13-2019, 04:12 PM | #26 |
Wizard
Posts: 1,539
Karma: 6613969
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
|
|
11-13-2019, 04:18 PM | #27 | ||
Wizard
Posts: 1,539
Karma: 6613969
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
|
Yes, but when you are in need...
Quote:
Code:
div.poem { float: left; width: 100%; page-break-inside: avoid; } Quote:
|
||
11-13-2019, 07:52 PM | #28 |
Grand Sorcerer
Posts: 6,494
Karma: 84420419
Join Date: Nov 2011
Location: Tampa Bay, Florida
Device: Kindles
|
I don't think that will work. In my testing the page-break-avoid seems to only be effective if used with a relatively small width. The details of this are mysterious.
|
11-13-2019, 08:03 PM | #29 | |
Resident Curmudgeon
Posts: 73,840
Karma: 128597114
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
Code:
body { widows: 1; orphans: 1; margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; text-align: justify; } |
|
11-13-2019, 09:19 PM | #30 | |
Wizard
Posts: 1,539
Karma: 6613969
Join Date: Mar 2013
Location: Rosario - Santa Fe - Argentina
Device: Kindle 4 NT
|
Quote:
Code:
<h2>My Title</h2> <h3>My Subtitle</h3> <p>Some text here ... </p> Code:
<h2>My Title</h2> <div class="joint"> <h3>My Subtitle</h3> <p>Some text here ... </p> </div> Code:
.joint { float: left; width: 100%; page-break-inside: avoid; } |
|
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Widows and Orphans | Calenorn | Kobo Reader | 3 | 10-21-2019 10:52 AM |
Content Widows and Orphans on Kindle | cc_in_oh | Amazon Kindle | 3 | 08-11-2016 11:38 AM |
Pagebreak, widows and orphans | UncleIvor | ePub | 17 | 09-11-2015 11:12 AM |
Touch Widows and Orphans and firmware, oh my! | MacEachaidh | Kobo Reader | 5 | 05-02-2013 11:14 AM |
Widows and Orphans | danrodney | ePub | 10 | 12-08-2010 02:08 PM |