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 788909 - Zoom level capped too low on HiDPI display
Zoom level capped too low on HiDPI display
Status: RESOLVED DUPLICATE of bug 303365
Product: evince
Classification: Core
Component: general
3.26.x
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-10-13 05:12 UTC by Victor Engmark
Modified: 2018-05-14 21:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Victor Engmark 2017-10-13 05:12:04 UTC
I believe this is different from bug #753220.

With Xft.dpi at 276 (actual resolution) and using xrandr to scale 1.5x1.5, a typical A4 PDF's zoom level is soft capped at about 320%. I say "soft" because it turns out if I zoom in and out fast enough (by holding down Ctrl and moving two fingers on the touchpad) I can get somewhat higher zoom levels, up to 383% with a quick test. However, at the default max of 320% the displayed file is still somewhat smaller than the paper when printed. At 383% it's about the same size as printed. With an A2 (420 × 594 mm) single-page PDF the zoom level is capped at about 160%. This means the page doesn't even fill the whole screen in fullscreen mode, and the contents are completely illegible. The caps on the zoom levels should therefore be changed to be *much* higher than they currently are.

Ideally zoom level 100% (without xrandr scaling) should always make the document display as big as it would be in physical form, and zooming should be capped at maybe two orders of magnitude outside that (1%-10000%).
Comment 1 Germán Poo-Caamaño 2018-05-14 21:22:56 UTC
This seems a duplicate of Bug 303365

The limitations are explained there. HiDPI exacerbates the need for a fix.

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