Quote:
|
And I still see the "long paragraph" and "one page break before the last paragraph at the end of random chapters" bug.
|
The "long paragraph" etc. bug should be fixed with those settings. I tested it months ago with problematic books and haven't it experienced it since I added it to my conversion patterns.
Quote:
|
I add this to the CSS in Calibre but am curious - does this give you full lines right to the bottom of the screen on every page? I still see some pages with one blank line at the bottom.
|
You can't claim the full screen space in the original reader app. You have always a wasted space at the bottom that is about as big as the menu bar you get when tapping the screen.
If you want real full screen text, there is a port of the kindlepdfreader in the devforum, which offers it. Sadly it's not based on the newer version which is better suited for touchscreen devices, but it's useable.
Quote:
Originally Posted by JSWolf
I do have widows and orphans both set to 0 in the body CSS style. Could this be another case of lets ignore it in the body style?
In the v1 sample, there is just 1 line left of the paragraph. It would have easily fit on the screen.
I'll try putting the widows and orphans in the p style and post v1 again for another sample look.
|
Quite possible, that's why I add it to <p> aswell, Kobo css interpretation is a bit temperamental/weird at times.
Quote:
|
Edit : I went through the whole book and there is one place where you end up with just three lines on a page (p. 25) not sure those three lines could fit on the previous page if you used widows 0 and orphans 0 settings, there is one other place where there are just 4 lines on the page (p. 97) they for sure would not fit on the previous page unless they went over top of the page numbers at the bottom. so at most I think you might save one page turn in the whole book by using widows 0 and orphans 0, not sure it would be worth the effort.
|
The example is a well formatted book.
If you have one with bad formatting you might end up with the few lines per page bug every 10 pages or so. It happens very rarely and the book must be really screwed up, but it can happen.
The real benefit is for me that you usually get one or two lines text more on the screen with the value set, then otherwise.
Looking at your Screenshot, the empty at the bottom looks rather big compared to my Glo.