Description of problem: The current liberation-fonts package is built by fontforge 20160404 and results in the top of the fonts being chopped off in some pages in Chrome/Chromium. For example, with this page: https://www.reddit.com/r/linux/comments/600h4f/wine_24_released/ When built with fontforge 20160404: http://i.imgur.com/kO2H3Hw.png When built with fontforge 20150430: http://i.imgur.com/IQmu5o3.png Notice how the first line of pixels is getting chopped off. Version-Release number of selected component (if applicable): liberation-fonts-common-1.07.4-7.fc24.noarch liberation-mono-fonts-1.07.4-7.fc24.noarch liberation-sans-fonts-1.07.4-7.fc24.noarch liberation-serif-fonts-1.07.4-7.fc24.noarch fontforge-20160404-5.fc25.x86_64 Additional info: I did a git bisect and found that this is the commit in fontforge that introduced the issue. --- [chenxiaolong@cxl-fedora25vm fontforge]$ git bisect bad e870019c2602d50eb00793e979f3e11bcc71d6cf is the first bad commit commit e870019c2602d50eb00793e979f3e11bcc71d6cf Author: Frédéric Wang <fred.wang> Date: Wed May 13 08:03:13 2015 +0200 Fix read/write of bits USE_TYPO_METRICS and WWS for OS2 version < 4 :040000 040000 7032ea971c1d084ab8a038b4a80d9092e53a8519 eb11e4b5a69718ad94d8dbfc414e7b2a944548d3 M fontforge --- https://github.com/fontforge/fontforge/commit/e870019c2602d50eb00793e979f3e11bcc71d6cf Is this something that can be fixed without affecting/breaking other fonts?
By the way, my screenshots are of the proprietary Google Chrome, but the same behavior occurs with Chromium from the Fedora repos (56.0.2924.87-3.fc25.x86_64).
Can you report this issue on upstream fontforge as well? https://github.com/fontforge/fontforge/issues/ Lets see whats upstream says about it.
Absolutely. I'll make the upstream bug report after work and link it here.
I have reported the issue upstream here: https://github.com/fontforge/fontforge/issues/3052
You can also notice this bug when marking / selecting those fonts in Firefox.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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.
I changed the target version to 27 since this still affects the latest Fedora release.
Could you confirm if this still happens with fontforge-20170731?
Thank you for the reply, Jens. I just recompiled the liberation-fonts RPMs against fontforge-20170731-2.fc27.x86_64 and it seems the issue still exists. When visiting the following page: https://www.reddit.com/r/rust/comments/7ew6a6/announcing_rust_122_and_1221/ with either of the following browsers: * chromium-62.0.3202.89-1.fc27.x86_64 * google-chrome-stable-62.0.3202.94-1.x86_64 I get the following results: * Built against fontforge 20170731: https://i.imgur.com/koJXJzn.png * Built against fontforge 20150430: https://i.imgur.com/UhRZNv4.png (The missing line of pixels is most noticeable around the "49 points" text.)
This seems to be reproducible on my new laptop with a 4K screen. At GNOME's default 2x scale factor, the top 2 rows of pixels are chopped off instead of just the top row. On the HiDPI screen, it's no longer easily noticeable, but the issue is definitely still there. I've made a side-by-side comparison screenshot with the two fontforge versions: https://i.imgur.com/vW5L0K3.png
This was finally fixed by https://bugzilla.redhat.com/show_bug.cgi?id=1526510 (version 1.07.4-10.fc27.noarch).