Created attachment 1446164 [details] screen shows fontlint error Description of problem: fontlint commad reports error related to 2 self-intersecting glyphs, 3 wrong direction, 33 bad glyph name for DejaVusans.ttf Version-Release number of selected component (if applicable): related to self-intersecting glyphs, wrong direction, bad glyph name How reproducible: All time Steps to Reproduce: 1. Install fedora gold with ru_RU locale 2. Install fontforge package 3. and check default font 4. fontlint /usr/share/fonts/dejavu/DejaVuSans.ttf 5. Observe the errors Actual results: fontlint reports the error Expected results: fontlint should not report error for default fonts Additional info: attached screen captured Error : [root@localhost ~]# fontlint /usr/share/fonts/dejavu/DejaVuSans.ttf Copyright (c) 2000-2014 by George Williams. See AUTHORS for Contributors. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> with many parts BSD <http://fontforge.org/license.html>. Please read LICENSE. Based on sources from 21:59 UTC 11-Feb-2018-ML-D. Based on source from git with hash: Attempt to unget two characters CHECKING /usr/share/fonts/dejavu/DejaVuSans.ttf Это шрифт содержит как таблицу 'kern', так и таблицу 'GPOS'. Таблица 'kern' читается только если функции 'kern' нет в 'GPOS'. Use-my-metrics flag set on at least two components in glyph 685 The glyph named Omega is mapped to U+03A9. But its name indicates it should be mapped to U+2126. ERROR 2 Self-intersecting glyph ERROR 3 Wrong direction ERROR 5 Missing points at extrema ERROR 33 Bad 'glyf' or 'loca' table FAIL /usr/share/fonts/dejavu/DejaVuSans.ttf
Good to report this issue to upstream as well.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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.
Still same issue in Fedora-30. IMO lets report this in upstream and close as a upstream. Lets upstream decide whether they want to fix it or not.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. 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 '30'. 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 30 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 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.