Bug 480910 - Fonts in Evince at 100% zoom are very blurry compared to the same in gv
Summary: Fonts in Evince at 100% zoom are very blurry compared to the same in gv
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: evince
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jonathan Blandford
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-01-21 10:22 UTC by D.S. Ljungmark
Modified: 2013-04-02 04:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-18 07:39:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Screenshot showing the issue (24.80 KB, image/png)
2009-01-21 10:23 UTC, D.S. Ljungmark
no flags Details
The same in ghostview (83.22 KB, image/png)
2009-01-21 10:23 UTC, D.S. Ljungmark
no flags Details
Correct screenshot of Evince (121.28 KB, image/png)
2009-01-21 10:55 UTC, D.S. Ljungmark
no flags Details

Description D.S. Ljungmark 2009-01-21 10:22:24 UTC
Description of problem:
gv is the de facto old standard viewer of pdf/ps files, but the newer evince is filling it quite nicely, except that the default fonts are nearly unreadable due to the excessive amount of antialiasing/blurring applied to them.

While my fonts are fine on the actual desktop and in editing, in evince it is nearly impossible to read them.



Version-Release number of selected component (if applicable):
poppler-0.8.7-1.fc10.i386
evince-2.24.2-1.fc10.i386

How reproducible:
install samba-doc , evince and gv
open the Samba3-HOWTO.pdf and compare the visual looks

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 D.S. Ljungmark 2009-01-21 10:23:16 UTC
Created attachment 329579 [details]
Screenshot showing the issue

Uploading screenshots to compare.

Comment 2 D.S. Ljungmark 2009-01-21 10:23:51 UTC
Created attachment 329580 [details]
The same in ghostview

Comment 3 D.S. Ljungmark 2009-01-21 10:55:17 UTC
Created attachment 329587 [details]
Correct screenshot of Evince

Seems I uploaded the wrong screenshot the first time, this one is the correct one.

Comment 5 Bug Zapper 2009-11-18 10:48:47 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2009-12-18 07:39:50 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.