|
![]() |
|
Thread Tools | Search this Thread |
![]() |
#16 | |||
Junior Member
![]() Posts: 5
Karma: 10
Join Date: Jul 2017
Device: Kindle
|
Quote:
Quote:
Quote:
Last edited by Veelk; 08-01-2017 at 09:01 AM. |
|||
![]() |
![]() |
![]() |
#17 | ||
A Hairy Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,355
Karma: 20171571
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
|
Quote:
Quote:
|
||
![]() |
![]() |
Advert | |
|
![]() |
#18 |
Junior Member
![]() Posts: 5
Karma: 10
Join Date: Jul 2017
Device: Kindle
|
Okay, I managed to get it to work on seemingly most of my ebooks...except the one I am currently reading. So, if I have confirmation that it does indeed work on some, how do I get it to work on others?
Edit: okay, testing it out some more, some books adhere to it and I can see clear gaps at the bottom that indicate that the program pushes the paragraphs to the next page. Other books don't care and just do nothing. It feels like older books are more prone to this than newer. Last edited by Veelk; 08-04-2017 at 11:12 AM. |
![]() |
![]() |
![]() |
#19 | |
Bookmaker & Cat Slave
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
And I'm not saying that this is good or bad, BUT, we are finding a massive shift in print from perfectly aligned pages without any widows and orphans to a mindset that doesn't seem to care about w/o, telling us to ignore the w/o issue in order to square the page. {shrug} I guess that those of us who still find it vexing, to see w/o and unsquared pages are just old fogies. :-) Oh, and the widows/orphans thing, in eBooks--in about 50-70% of them, it doesn't work. If you're on iOS, fine (or Kobo, b/c they've mooched a lot of the iOS rendering engine, which in turn had originally moooched ADE...), or Readium or Azardi, but after that, rotsa ruck. Hitch |
|
![]() |
![]() |
![]() |
#20 |
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 79,763
Karma: 145864619
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
I prefer windows and orphans set to 1 so we do get pages ending at the same place in most pages.
|
![]() |
![]() |
Advert | |
|
![]() |
#21 |
Fanatic
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 557
Karma: 400004
Join Date: Feb 2009
Device: ONYX M96
|
As Betterred said you can "ask" to do not break paragraph using the page-break-inside CSS rule. But every ebook reader application could or not use it.
|
![]() |
![]() |
![]() |
#22 | |
Bibliophagist
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 46,273
Karma: 168983734
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Quote:
In one example, you have a paragraph which takes 8 lines with 7 at the bottom of the display and 1 carried over to the next page. A setting of widows=2 would force another line to the next page splitting the paragraph 6 lines/2 lines. I've seen some references that reverse widows and orphans from the definitions I've used but à chacun son goût. |
|
![]() |
![]() |
![]() |
#23 | |
Bibliophagist
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 46,273
Karma: 168983734
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Quote:
For what it's worth, the RMSDK renderer respects widows/orphans with a default of 2/2 if not overwritten in the CSS while the ACCESS renderer disregards them (equivalent to setting both to 1) so if you are seeing widows/orphans affecting the display on a Kobo ereader, you're using RMSDK. |
|
![]() |
![]() |
![]() |
#24 | |
Bookmaker & Cat Slave
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
If they haven't mooched some of the rendering settings, etc., from iBooks, the whole FXL thing is fairly remarkable. And truly--didn't mean to discuss iBooks; I was talking about the relative uselessness of the w/o settings. Hitch |
|
![]() |
![]() |
![]() |
#25 |
Resident Curmudgeon
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 79,763
Karma: 145864619
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
having widows & orphans other than a value of 1 is just silly on a screen. It's not the same as print and it just doesn't work. Many people don't care about how the paragraph splits. They care about how the page looks and to me, it looks silly when there is a varying amount of wasted space at the bottom of the screen because of widows & orphans.
|
![]() |
![]() |
![]() |
#26 |
A Hairy Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 3,355
Karma: 20171571
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
|
Personally I could care less about widows and orphans as I use the scroll mode instead of "pages"!
![]() |
![]() |
![]() |
![]() |
#27 |
Bookmaker & Cat Slave
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
|
![]() |
![]() |
![]() |
#28 | |
mostly an observer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,519
Karma: 987654
Join Date: Dec 2012
Device: Kindle
|
Quote:
So you have a paragraph beginning with a quote. The third sentence carries over to the next "page." So the second sentence almost certainly ends with a short line, which telegraphs to the reader that the paragraph has ended. Now we turn the "page" and find that the apparent next paragraph not only isn't indented (as you predict will happen) but doesn't begin with the quotation mark -- but ends with one! I see a very confused reader. It would be rather like reading a Bernie Gunther novel, which is forever changing speakers within the same paragraph, requiring me to go back and do a mental he said / she said to figure out who's talking. The whole thing is idiotic. What's wrong with a carry-over line of four words or even one? |
|
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
calibre new feature proposal - avoid breaking paragraph | rjwse@aol.com | Conversion | 9 | 03-17-2016 08:26 PM |
Preventing images breaking across pages | verydeepwater | ePub | 12 | 05-16-2014 01:00 PM |
wrong split paragraph | mikichi | Conversion | 3 | 01-25-2014 02:12 PM |
Pages Not Breaking | msmith65 | Sigil | 8 | 08-21-2012 12:32 PM |
Kindle Displaying Paragraph Indents Wrong | nbluedorn | Kindle Formats | 1 | 07-09-2011 03:27 PM |