[Bug 1509790] New: fc-query is generating weird 'id 0' Provides on
fonts
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1509790
Bug ID: 1509790
Summary: fc-query is generating weird 'id 0' Provides on fonts
Product: Fedora
Version: 26
Component: fontconfig
Severity: high
Assignee: tagoh(a)redhat.com
Reporter: ngompa13(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, alexl(a)redhat.com,
caillon+fedoraproject(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
john.j5live(a)gmail.com, mbarnes(a)fastmail.com,
mclasen(a)redhat.com, pnemade(a)redhat.com,
rhughes(a)redhat.com, rstrode(a)redhat.com,
sandmann(a)redhat.com, tagoh(a)redhat.com
Description of problem:
When I use fc-query to query a font, I get a weird item "id 0" in the list of
things returned back from fc-query.
This is screwing up dependency generation for new font packages, which get an
annoyingly awful "Provides: 0" added to the package.
Version-Release number of selected component (if applicable):
2.12.6-3.fc26
How reproducible:
Always
Steps to Reproduce:
1. Install google-noto-sans-fonts (or any other TrueType/OpenType font package)
2. Run "fc-query --format '%{=pkgkit}'
/usr/share/fonts/google-noto/NotoSans-Regular.ttf" (or your preferred fonts)
Actual results:
[~]$ fc-query --format '%{=pkgkit}'
/usr/share/fonts/google-noto/NotoSans-Regular.ttf
id 0
font(notosans)
font(:lang=aa)
...
Expected results:
[~]$ fc-query --format '%{=pkgkit}'
/usr/share/fonts/google-noto/NotoSans-Regular.ttf
font(notosans)
font(:lang=aa)
...
Additional info:
This doesn't occur in RHEL 7 (fontconfig-2.10.95-11.el7) nor openSUSE Leap 42.2
(fontconfig-2.11.1-2.2) nor Fedora 25 (fontconfig-2.12.1-1.fc25), but occurs in
Fedora 26 and newer.
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 4 months
[Bug 1513011] New: freetype-devel.i686 caused pkgconf downgrade
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1513011
Bug ID: 1513011
Summary: freetype-devel.i686 caused pkgconf downgrade
Product: Fedora
Version: 27
Component: freetype
Assignee: mkasik(a)redhat.com
Reporter: litimetal(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, alexl(a)redhat.com,
caillon+fedoraproject(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
john.j5live(a)gmail.com, kevin(a)tigcc.ticalc.org,
mbarnes(a)fastmail.com, mclasen(a)redhat.com,
mkasik(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com
Created attachment 1352027
--> https://bugzilla.redhat.com/attachment.cgi?id=1352027&action=edit
dnf.log
Description of problem:
Version-Release number of selected component (if applicable):
freetype-devel i686 2.8-6.fc27
How reproducible:
Every time
Steps to Reproduce:
1. sudo dnf install freetype-devel.i686
2.
3.
Actual results:
Downgrading:
libpkgconf pkgconf pkgconf-m4 pkgconf-pkg-config
Expected results:
Additional info:
$ rpm -q pkgconf
pkgconf-1.3.10-1.fc27.x86_64
$ rpm -q freetype-devel
freetype-devel-2.8-6.fc27.x86_64
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 4 months
[Bug 1469712] New: font antialiasing/hinting is not working on
Fedora 26
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1469712
Bug ID: 1469712
Summary: font antialiasing/hinting is not working on Fedora 26
Product: Fedora
Version: 26
Component: freetype
Severity: high
Assignee: mkasik(a)redhat.com
Reporter: mchehab(a)infradead.org
QA Contact: extras-qa(a)fedoraproject.org
CC: behdad(a)fedoraproject.org,
fonts-bugs(a)lists.fedoraproject.org,
kevin(a)tigcc.ticalc.org, mkasik(a)redhat.com
Description of problem:
After upgrading from Fedora 25 to Fedora 26, font hinting doesn't work anymore.
All fonts look really ugly on my 32' monitor, and changing font antialias/hint
options at Gnome, Plasma or Mate doesn't produce any visible changes anymore.
With Fedora 25, I used freetype-freeword from rpmfusion, as it produced a
better result than the default freetype font hinting (although both work). On
Fedora 26, neither with or without freetype-freeword I can adjust font
hint/antialias anymore, as those options don't work anymore.
Version-Release number of selected component (if applicable):
freetype-2.7.1-9.fc26.x86_64
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 4 months
[Bug 1496761] "Noto Color Emoji"
would be a better default emoji font than "Emoji One"
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1496761
--- Comment #17 from Bastien Nocera <bnocera(a)redhat.com> ---
(In reply to Jeremy Bicha from comment #16)
> (In reply to Bastien Nocera from comment #15)
> > We know all this, but decided that it was the best solution for this purpose
> > already. There should be discussions about this on the Fedora Workstation
> > list, as well as in the GNOME bugzilla and/or wiki. If in doubt about any of
> > those, I'd be happy repeating those arguments on the fontconfig list, if you
> > send an email there and CC: me.
>
> 1. I don't think you've had these conversations as broadly as you remember.
<snip>
> To summarize your position since you didn't mention it here: You don't want
> to use the same emoji as Android because you see the emoji choice as a brand
> recognition opportunity. I'm not sure our users will see it the same way.
Again, not the place to discuss this. I discussed this with Allan and Jakub,
who agreed with this choice, Behdad and Akira, who both agreed to give EmojiTwo
time to be built for our purposes, which we hope would happen within the next
year.
Most of those discussions happened nearly a year ago, with much shorter
discussions around GUADEC this year to re-affirm that EmojiOne would be chosen.
Some of the discussions which I thought happened on the public fontconfig list
actually happened in private. I'm not sure why the fontconfig maintainer CC:ed
folks instead of making the discussion happen on the list.
In any case, that ship has sailed. If you want to ship something else in
Ubuntu, or Debian, it's easy enough to do. If you want to have a discussion
about the default choice, again, here is not the place.
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 4 months
[Bug 1496761] "Noto Color Emoji"
would be a better default emoji font than "Emoji One"
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1496761
--- Comment #16 from Jeremy Bicha <jbicha(a)ubuntu.com> ---
(In reply to Bastien Nocera from comment #15)
> We know all this, but decided that it was the best solution for this purpose
> already. There should be discussions about this on the Fedora Workstation
> list, as well as in the GNOME bugzilla and/or wiki. If in doubt about any of
> those, I'd be happy repeating those arguments on the fontconfig list, if you
> send an email there and CC: me.
1. I don't think you've had these conversations as broadly as you remember.
a. https://wiki.gnome.org/Design/OS/Emoji says nothing about preferring a
particular emoji font.
b. You shut this thread down immediately:
https://lists.fedoraproject.org/archives/list/desktop@lists.fedoraproject...
c. I haven't been able to find any fontconfig list discussion of this issue.
d. This bug has been closed without hardly any discussion, and they were
closed by a fix that appears to me to be side-stepping the actual bug report
and title.
e. There was an October 23 Fedora Workstation meeting. Based on my reading of
the logs, I think it's fair to say that if it wasn't for your opinion, the team
would have decided the other direction (Noto instead of EmojiOne).
2. As far as Fedora 27 goes, it looks like the Emoji One decision is final. Ok.
I understand freezes and Fedora is welcome to make its own decisions.
3. Here are my objections:
a. You have said repeatedly (in the fontconfig commit and the October 23
meeting) that Emoji One/Two is GNOME's preferred emoji font.
b. EmojiTwo in its current form is unpackagable. Comment #14 here gives hope,
but currently that is vaporware.
Therefore, I expect many GNOME distros to be choosing Noto Color Emoji and so I
object to the characterization that this is GNOME's decision because I believe
you didn't actually talk to other GNOME distros about this.
To summarize your position since you didn't mention it here: You don't want to
use the same emoji as Android because you see the emoji choice as a brand
recognition opportunity. I'm not sure our users will see it the same way.
--
You are receiving this mail because:
You are on the CC list for the bug.
5 years, 4 months