https://bugzilla.redhat.com/show_bug.cgi?id=1814349
--- Comment #5 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> ---
IMHO
http://gsdview.appspot.com/chromeos-localmirror/distfiles/crosextrafonts-20…
is a dead end evolution-wise.
Sure, you can continue using it, but it’s an orphaned no-upstream thing. So, at
some point, it will need switching out.
Also note that the coverage of the chromeos version, is less than the coverage
of the new upstream (granted, the github project is missing precomposed T WITH
CEDILLA; don’t know if this precomposition is a requirement in modern unicode).
And a lot of the other differences are trutype instructions missing in the
ChromeOS variant.
It looks like the ChromeOS version of the font files forked from an earlier
state of the project. Or, used the same design masters, but processed with
earlier 2013 font tools, a lot less complete than the ones available today.
Certainly, it seems to be missing a lot of things present in the github
version.
(like all Google font projects the new project forgets to remove Regular from
fullname; that hints at using common tooling with all the other Google fonts;
given the extent of Google font nowadays, I’d expect the result to be
significantly more robust than whatever ChromeOS used in 2013).
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1813578
Bug ID: 1813578
Summary: fontforge-20200314 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: fontforge
Keywords: FutureFeature, Triaged
Assignee: kevin(a)scrye.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org, kevin(a)scrye.com,
paul(a)frixxon.co.uk, pnemade(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 20200314
Current version/release in rawhide: 20190801-6.fc33
URL: https://github.com/fontforge/fontforge
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/5807/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1809062
Fedora Update System <updates(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |MODIFIED
--- Comment #7 from Fedora Update System <updates(a)fedoraproject.org> ---
FEDORA-2020-eef8e7dadd has been submitted as an update to Fedora 32.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-eef8e7dadd
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1815641
Bug ID: 1815641
Summary: fonttools-4.5.0 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: fonttools
Keywords: FutureFeature, Triaged
Assignee: pnemade(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
pnemade(a)redhat.com, sshedmak(a)redhat.com,
tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 4.5.0
Current version/release in rawhide: 4.4.3-1.fc33
URL: https://github.com/fonttools/fonttools/
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/7388/
--
You are receiving this mail because:
You are on the CC list for the bug.