https://bugzilla.redhat.com/show_bug.cgi?id=1690275
--- Comment #3 from Jens Petersen <petersen(a)redhat.com> ---
Please report this to upstream gnome gitlab.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1690275
Parag Nemade <pnemade(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|30 |32
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1401096
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |CURRENTRELEASE
Last Closed| |2020-04-07 06:04:36
--- Comment #7 from Jens Petersen <petersen(a)redhat.com> ---
I think langpacks auto- installation via gnome-software now takes care of this.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1380754
Parag Nemade <pnemade(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
CC| |pnemade(a)redhat.com
Resolution|--- |CANTFIX
Last Closed| |2020-04-07 06:03:08
--- Comment #8 from Parag Nemade <pnemade(a)redhat.com> ---
Well this package has been already retired from Fedora 27.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1076190
vishalvvr <vishalvijayraghavan(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vishalvijayraghavan(a)gmail.c
| |om
Version|30 |rawhide
Assignee|psatpute(a)redhat.com |vishalvijayraghavan(a)gmail.c
| |om
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1761089
Bug ID: 1761089
Summary: Request to package fcitx and other fcitx libraries on
EPEL 8
Product: Fedora EPEL
Version: epel8
Status: NEW
Component: fcitx
Assignee: liangsuilong(a)gmail.com
Reporter: jatin1812(a)protonmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, i(a)cicku.me,
liangsuilong(a)gmail.com, pwu(a)redhat.com,
robinlee.sysu(a)gmail.com
Target Milestone: ---
Classification: Fedora
We do have fcitx in EPEL 7 repos, RHEL 8/ CentOS 8 need fcitx in EPEL 8
repositories :)
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1090631
--- Comment #10 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> ---
Anyway Fedora fonts packaging guidelines have been updated now, and they
REQUIRE fedora font packages to follow the OpenType font model, not invent
alternative family definitions.
https://docs.fedoraproject.org/en-US/packaging-guidelines/FontsPolicy/#_pac…
Liberation Sans and Liberation Serif are not the same font family, they differ
in more than in width/weight/slant/optical sizing (you could even add OpenType
feature in there if you wanted the whole OpenType model as it exists now in
OpenType specs).
There is no Sans/Serif variation axis in OpenType, and the existing axis
already include quite experimental stuff like optical sizing.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1090631
vishalvvr <vishalvijayraghavan(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|30 |rawhide
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1084493
vishalvvr <vishalvijayraghavan(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vishalvijayraghavan(a)gmail.c
| |om
Version|30 |rawhide
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1072095
vishalvvr <vishalvijayraghavan(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vishalvijayraghavan(a)gmail.c
| |om
Version|30 |rawhide
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1814351
Parag Nemade <pnemade(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CLOSED
Fixed In Version| |google-carlito-fonts-1.103-
| |0.13.20130920.fc33
Resolution|--- |RAWHIDE
Last Closed| |2020-04-01 16:12:17
--- Comment #6 from Parag Nemade <pnemade(a)redhat.com> ---
Thank you for this package review.
Built this package in google-carlito-fonts-1.103-0.13.20130920.fc33 build.
As this font has been specified as optional font in Fedora comps file, reported
only https://pagure.io/fedora-comps/pull-request/479
--
You are receiving this mail because:
You are on the CC list for the bug.
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=1651736
Bhushan Barve <bbarve(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|31 |32
--- Comment #3 from Bhushan Barve <bbarve(a)redhat.com> ---
Updating the version to F32.
--
You are receiving this mail because:
You are on the CC list for the bug.