Version: (using KDE KDE 3.5.2) Installed from: SuSE RPMs It should be configurable -- currently is set to 0 and it is confusing reading documents with pgup and pgdn since there is always a reflex something was omitted. Note -- overlap should be defined in page metrics, not screen metrics (otherwise it would be magnification dependent).
*** This bug has been marked as a duplicate of 133693 ***
It is not duplicate. The other one didn't even mentioned overlapping.
There is: "It would be great to have an option to jump to the next page (like now) plus scroll a bit down the exact amount of pixels the current page is scrolled."
The other one is about defining viewport, so you could omit margins. This one, is another story (but does not conflict with viewport idea). Let's focus on 1 dimension. abcabcabc and say, we have window three letters wide. So now kpdf shows: abc abc abc but overlap would be useful to ensure user she/he sees all, for overlap=1 abc cab bca abc cab bca abc Again -- the other one is about how to get rid of empty space, this one is about readability.
They do conflicts, how can you keep the current viewport when switching to the next page, and adapt it to show an overlap, at the same time? Then either you don't do overlap, or you don't keep the viewport. Oh, and personally I'd avoid suggesting options and options and options for every bug report.
They do not conflict. Look -- you set that you DO NOT want to see margins, 1cm of each side. This is what the other report says. And now, I would set an overlap 5 cm. If you have page 11x11cm, you will see middle 9x9. Let's say you can see 7 cm at the screen. So at first step you will see 1-8, when you press pg-dn, 3-9 + 1-2 from the next page. And so on.
The other report is _not_ about setting margins, but about restoring the current vertical delta from the top of the shown page when switching to the next page. That's why they _do_ conflict. The idea of "margins" (that imho does not fit completely in the other bug report) comes directly from you. And remembering a verical delta and setting margins are different things.
(the other report) while setting "default" the shift per page is useful it is even more powerful to cut off the margins. So I focused on margins -- and margins cut-off does not conflict with overlap (btw. I sent both reports :-D, and cutting off margins fit, the point is to get only contents not the empty space).
*** This bug has been marked as a duplicate of 107544 ***