View Single Post
Old 09-29-2020, 03:37 AM   #31
Mrs_Often
Wizard
Mrs_Often ought to be getting tired of karma fortunes by now.Mrs_Often ought to be getting tired of karma fortunes by now.Mrs_Often ought to be getting tired of karma fortunes by now.Mrs_Often ought to be getting tired of karma fortunes by now.Mrs_Often ought to be getting tired of karma fortunes by now.Mrs_Often ought to be getting tired of karma fortunes by now.Mrs_Often ought to be getting tired of karma fortunes by now.Mrs_Often ought to be getting tired of karma fortunes by now.Mrs_Often ought to be getting tired of karma fortunes by now.Mrs_Often ought to be getting tired of karma fortunes by now.Mrs_Often ought to be getting tired of karma fortunes by now.
 
Mrs_Often's Avatar
 
Posts: 1,775
Karma: 2694823
Join Date: Dec 2011
Location: The Netherlands
Device: Kobo Touch, Glo, Clara HD
Quote:
Originally Posted by jackie_w View Post
I meant to reply to this earlier. It's not just widows/orphans which can cause a variable number of lines per page. In addition I think widows/orphans are ignored in kepubs.

It will also happen if the book's CSS styling for its standard paragraph has a non-zero top margin (however small). Compare the vertical gap between
- lines 1 and 2 of the same paragraph
- the last line of one paragraph and the first line of the next paragraph

If they're different then the number of visible lines-per-page will be more on a page containing just one very long paragraph versus a page full of conversational dialogue with a lot of short paragraphs.

The first line of every page always starts in exactly the same place but the last line on each page is going to vary in the scenario I outlined above.
Oh! That makes perfect sense! And the pics I shared show perfectly that the page with more paragraphs (and thus more before/after paragraph space) is the one that has less lines. Why didn't I think of that Stupid.

I don't like before/after paragraph space, also not in documents that I write myself, I always remove them. Would that be something your custom beta KePub stylesheet anchor style patch that you shared in the request patches thread could get rid of too?

EDIT to add: Haha, that's a really stupid question, seeing your beta patch is for the anchor style specifically. Somehow, I'd got it into my head that the patch was for changing kepub CSS in general

Quote:
To compensate you might want to reduce the height even further in the Reduce new header/footer height patch. What values are you currently using and for which device?
I just have the standard 33% reduction for Clara HD:
Code:
        # AuraHD/H2O/GloHD/ClaraHD (Dragon)
      - Find:    "ReadingFooter[qApp_deviceIsDragon=true] {\n  min-height: 101px;\n  max-height: 101px;\n}"
        Replace: "ReadingFooter[qApp_deviceIsDragon=true] {\n  min-height: 66px;\n  max-height: 66px;\n}"
I didn't dare make it smaller because that would make the header smaller too... did I understand that correctly? Or would it not show as much as a possible extra line on the bottom would show? What values do you suggest I try? I don't fully understand how to change the values, because the comments also state "Keep min-height=max-height", whatever that means...

Last edited by Mrs_Often; 09-29-2020 at 04:41 AM.
Mrs_Often is offline   Reply With Quote