12-14-2019, 12:25 AM | #61 |
just an egg
Posts: 1,587
Karma: 4300000
Join Date: Mar 2015
Device: Kindle, iOS
|
|
12-14-2019, 11:12 AM | #62 |
Bookmaker & Cat Slave
Posts: 11,462
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
|
Advert | |
|
12-14-2019, 11:27 AM | #63 |
Resident Curmudgeon
Posts: 74,037
Karma: 129333114
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Here is the link to the Kobo patch thread for the 4.19.x firmware.
https://www.mobileread.com/forums/sh...d.php?t=325572 |
12-14-2019, 11:28 AM | #64 | |
Resident Curmudgeon
Posts: 74,037
Karma: 129333114
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
|
|
12-14-2019, 11:49 AM | #65 |
Grand Sorcerer
Posts: 6,212
Karma: 16534894
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
No, you're wrong about that. The calibre KoboTouch/KoboTouchExtended drivers do not distinguish between epub and kepub if you have configured them to make auto-changes to widows/orphans on-the-fly during send-to-device.
If you only read kepub then you don't really need this option because the kepub renderer either doesn't use widows/orphans or always sets them to 1 (I don't know which). |
Advert | |
|
12-18-2019, 11:01 AM | #66 | |
Grand Sorcerer
Posts: 6,498
Karma: 84420419
Join Date: Nov 2011
Location: Tampa Bay, Florida
Device: Kindles
|
Quote:
Regular paragraphs of text can be kept together in their entirety. Applying this property to a span appears to do nothing. Applying it to a div containing multiple paragraphs and a full width image causes them to all be kept together when shown in the Previewer. However on a Kindle running the 5.13.3 firmware the individual paragraphs are kept together but page breaks still occur between them. |
|
12-18-2019, 01:53 PM | #67 | |
Bookmaker & Cat Slave
Posts: 11,462
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
But we don't yet know what happens in a for-sale book that's been through the PW? (Publishing Workflow)? Hitch |
|
12-18-2019, 04:14 PM | #68 | |
Grand Sorcerer
Posts: 6,498
Karma: 84420419
Join Date: Nov 2011
Location: Tampa Bay, Florida
Device: Kindles
|
Quote:
My test was done using an EPUB converted for Enhanced Typesetting in the Kindle Previewer and using a sideloaded KFX file on a Kindle Oasis which produced from the KPF file exported by the Previewer. I did not test MOBI or KF8 since I don't think anything has changed with the renderers for those formats. As far as I know they ignore page-break-inside:avoid, but I would be happy to find out if I am wrong about that. That is correct. I don't yet know what happens there. |
|
12-18-2019, 05:07 PM | #69 | |
Bookmaker & Cat Slave
Posts: 11,462
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
Hitch |
|
12-18-2019, 06:58 PM | #70 | |
Wizard
Posts: 1,551
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> |
|
12-18-2019, 07:44 PM | #71 |
Grand Sorcerer
Posts: 6,498
Karma: 84420419
Join Date: Nov 2011
Location: Tampa Bay, Florida
Device: Kindles
|
|
12-18-2019, 08:51 PM | #72 | |
Grand Sorcerer
Posts: 6,498
Karma: 84420419
Join Date: Nov 2011
Location: Tampa Bay, Florida
Device: Kindles
|
Quote:
I took a random sample of nine recently published novels. Four of those nine books contain the KFX equivalent coding for page-break-inside:avoid. For two of those I looked at the KF8 format HTML and was able to verify that the publishers had coded those books with page-break-inside:avoid in some styles and that those had carried though to KFX format. |
|
12-19-2019, 08:51 AM | #73 | |
Bookmaker & Cat Slave
Posts: 11,462
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
Well...hmph. I guess that means we'll have to include it in places where we previously didn't, as needed; we've had it for dog's years, as future-proofing. Hitch |
|
12-19-2019, 09:34 AM | #74 |
Grand Sorcerer
Posts: 6,498
Karma: 84420419
Join Date: Nov 2011
Location: Tampa Bay, Florida
Device: Kindles
|
The examples where I saw it yesterday were mostly from stock stylesheets. The most common usage was to prevent page breaks within headings. While adding that does not hurt, it probably also does not help much either since the default KFX widow/orphan handling will prevent page breaks for headings of three lines or less anyway.
|
12-19-2019, 09:40 AM | #75 |
Resident Curmudgeon
Posts: 74,037
Karma: 129333114
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
I never understood the read for adding CSS to avoid page breaks for headers (aka chapter headings).
|
|
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 |