After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 567626 - Evince should centralize Ebooks in two page mode
Evince should centralize Ebooks in two page mode
Status: RESOLVED DUPLICATE of bug 169676
Product: evince
Classification: Core
Component: general
2.24.x
Other All
: Normal enhancement
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-01-13 17:20 UTC by Martin Mai
Modified: 2013-06-15 06:35 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Martin Mai 2009-01-13 17:20:13 UTC
Originally reported on https://bugs.launchpad.net/ubuntu/+source/evince/+bug/308174:

I use evince in two page mode as an ebook viewer. Most ebook have a broad rim. I can't cut out this useless rim in two page mode, and consequently, both double pages are shifted to the right side. I can correct this by using the stroke keys, but every time I scroll to the next double page, the ebook is shifted to the right side once again. That is enervating!

It would make much more sense, if evince could centralice the ebook! This would make evince much better for ebook reading.
Comment 1 Jacek Chrzaszcz 2009-04-02 15:37:14 UTC
I second this feature wish. It is not only related to ebooks but to "normal" pdfs (e.g. scientific papers) with margins as well. 

The simplest way to do it would be to have a configuration panel where the user could specify how much margin he wants evince to "eat" on each side of the page.
Some visuale hackery or automatic detection would also be nice, but are not essential.

Bests

Jacek
PS. This is a feature Acrobat Reader does not have!
Comment 2 John Heidemann 2011-11-30 00:15:02 UTC
is this bug (yet another!) duplicate for bug #169676? :-(
Comment 3 Germán Poo-Caamaño 2013-06-15 06:35:03 UTC
Indeed.

*** This bug has been marked as a duplicate of bug 169676 ***