![]() |
#1 |
Junior Member
![]() Posts: 2
Karma: 10
Join Date: Sep 2017
Location: Russia
Device: Kobo Aura ONE
|
Getting rid of the Bottom Margin's Blank Space
Hello Everyone. I found the way to eliminate that pesky blank space. (I search through internet but didn’t find any answer for this. So I decided to make a post.) Here are a few steps: 1. For PC: Go to the Koreader folder on your device, open the defaults.lua and change DCREREADER_CONFIG_B_MARGIN_SIZES_SMALL to -15. 2. For Ereader: Summon the Main Menu, select the bottom tab with margin settings and set the bottom margin default value to -15 by pressing on the leftmost box. I hope it will help someone. Is there another way to get rid of it? |
![]() |
![]() |
![]() |
#2 |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,492
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
(In a document): Top Menu > Gear > Status bar > Settings > Reclaim bar height from bottom margin
That'll ensure a 0 bottom margin will actually be 0. Whether you do get a final line of text in here is subject to whether CRe decides it has enough space to do so or not given the current font settings ![]() I don't *think* it actually supports negative margins, in which case what you just did was just a roundabout way of negating the status bar height, but I very well might be wrong ![]() Last edited by NiLuJe; 01-15-2020 at 12:57 PM. |
![]() |
![]() |
Advert | |
|
![]() |
#3 |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,492
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
Also, defaults can be edited from within KOReader itself (Advanced settings, in the File Manager. It's in the Gear or Tools tab, I can't recall)
![]() |
![]() |
![]() |
![]() |
#4 |
Junior Member
![]() Posts: 2
Karma: 10
Join Date: Sep 2017
Location: Russia
Device: Kobo Aura ONE
|
Thank you for reply and tips!
![]() But the downside of having "Reclaim bar height from bottom margin" checked is inconsistent bottom margin. ![]() |
![]() |
![]() |
![]() |
#5 |
cosiñeiro
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,316
Karma: 2200073
Join Date: Apr 2014
Device: BQ Cervantes 4
|
The margin is consistent: 0. The distance between the last line displayed on that page and the bottom will be < the height of a line of text + surrouding space.
|
![]() |
![]() |
Advert | |
|
![]() |
#6 |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,492
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
Which, in your examples, happen to fall just right when there's a bit of extra layout-provided vertical space (title, blockquotes), but not with only paragraphs, where it might be missing a very few pixels.
The usual process involves decreasing/increasing the *top* margin (increasing it will shift content to the bottom, balancing the top/bottom white space, while decreasing it might be enough to free enough space to squeeze that last line in) until you find something that works okay. And/or play with font sizes & line height. That said, the fact that it behaved differently with a negative margin prooobably means we can lie to CRe. Which could arguably be construed as a bug, because it really shouldn't render to a larger buffer than the screen's ^^. I'll have to look into it one of these days. Last edited by NiLuJe; 01-15-2020 at 07:43 PM. |
![]() |
![]() |
![]() |
#7 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,653
Karma: 730583
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
|
@NiLuJe On the contrary, CREngine used to have a bug where it didn't do negative margins, see https://github.com/koreader/crengine/pull/299
(Probably not relevant to this particular margin here but either way I consider negative margins integral to getting the display you want.) |
![]() |
![]() |
![]() |
#8 |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,492
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
Margins might have been the wrong word ^^.
IIRC, we feed CRe a rectangle, computed after *our* margins are applied. That's what it uses to draw to. If *that* doesn't clamp to device's screen-size, *that* could be construed as a bug ;p. (i.e., once we blit that back to screen, the extra bottom rows are essentially "lost". Which works out okay for this purpose, but, could be interpreted as undefined behavior ![]() |
![]() |
![]() |
![]() |
#9 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,653
Karma: 730583
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
|
Right, so depending on what it actually does it could be a (seemingly benign) bug.
|
![]() |
![]() |
![]() |
Tags |
blank space, bottom margin, koreader |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Top-margin (bottom-margin?) for Kobo? | Notjohn | Sigil | 14 | 02-28-2015 06:43 AM |
@page { margin-bottom: 5.000000pt; margin-top: 5.000000pt; } | cybmole | Conversion | 15 | 02-12-2011 11:57 AM |
Can't get rid of bottom margin in epubs | ShellShock | Sony Reader | 3 | 02-11-2010 04:15 PM |
calibre ignore margin-top and margin-bottom | bender | Calibre | 2 | 12-11-2009 06:58 AM |
RTF Settings and blank space at the bottom of the page | Greg G | Sony Reader | 2 | 10-10-2006 05:31 AM |