Description of problem: Freetype incorporated a new rendering engine from adobe for cff/opentype fonts which incorporates a feature called "stem darkening". It's on by default and interacts badly with poppler currently so that CFF fonts are rendered with extremely dark ("bold"-looking) glyphs, this affects okular and evince (and others?) which rely on poppler. I've suggested to the poppler developers that they turn stem darkening off (freetype exposes this as runtime tweakable) by default in the library. But, even if they do, this will probably not fix it for defora 20 users, and I'd like to suggest fedora make this change as a distro patch for poppler. See: https://bugs.freedesktop.org/show_bug.cgi?id=78990 Version-Release number of selected component (if applicable): 0.24.3 How reproducible: View A pdf file containing an embedded cff (as opposed to ttf) font, the cff font appears much darker then the same font embedded as truetype. Steps to Reproduce: 1. I've uploaded an Example pdf and screenshots 2. open it in okular or evince. Actual results: The upper row (cff font) appars "bold" even though it's the same font and weight ad the lower row (ttf embedded font). Expected results: cff should not appear much darker then ttf fonts, simply because of the embedded format. Additional info: Poppler upstream issue: https://bugs.freedesktop.org/show_bug.cgi?id=78990 Freetype upstream issue: https://savannah.nongnu.org/bugs/index.php?42406 Original okular issue: https://bugs.kde.org/show_bug.cgi?id=335058
Created attachment 903090 [details] pdf file for repro
Created attachment 903091 [details] screenshot demonstrating the problem
Created attachment 903092 [details] screenshot demonstraing the effects of turning off stem darkening in FT2
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.