[Bug 1786596] New: Vertical alignment is off with PANGO_GRAVITY_EAST
and PANGO_GRAVITY_HINT_LINE
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1786596
Bug ID: 1786596
Summary: Vertical alignment is off with PANGO_GRAVITY_EAST and
PANGO_GRAVITY_HINT_LINE
Product: Fedora
Version: 31
OS: Linux
Status: NEW
Component: pango
Assignee: pwu(a)redhat.com
Reporter: abetakehiko(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: 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, mclasen(a)redhat.com,
pwu(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com,
tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Japanese chars and Latin chars in the same line do not vertically align when
the pango context's gravity is set to PANGO_GRAVITY_EAST and its hint set to
PANGO_GRAVITY_HINT_LINE.
Version-Release number of selected component (if applicable):
pango-1.44.7-1.fc31.x86_64
How reproducible:
Always
Steps to Reproduce:
pango-view --text="あーいうえお abcde" --gravity east --gravity-hint line
--font="NotoSerifJP 24"
Actual results:
Japanese chars and Latin chars in the same line do not vertically align.
Expected results:
Japanese chars and Latin chars in the same line vertically align as before.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 8 months
[Bug 1752788] New: CVE-2015-9381 freetype: a heap-based buffer
over-read in T1_Get_Private_Dict in type1/t1parse.c leading to information
disclosure
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1752788
Bug ID: 1752788
Summary: CVE-2015-9381 freetype: a heap-based buffer over-read
in T1_Get_Private_Dict in type1/t1parse.c leading to
information disclosure
Product: Security Response
Hardware: All
OS: Linux
Status: NEW
Component: vulnerability
Keywords: Security
Severity: medium
Priority: medium
Assignee: security-response-team(a)redhat.com
Reporter: mrehak(a)redhat.com
CC: ajax(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,
mclasen(a)redhat.com, mkasik(a)redhat.com,
rhughes(a)redhat.com, rstrode(a)redhat.com,
sandmann(a)redhat.com
Target Milestone: ---
Classification: Other
FreeType before 2.6.1 has a heap-based buffer over-read in T1_Get_Private_Dict
in type1/t1parse.c.
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 10 months
[Bug 1774474] New: Missing some coverage in certain variants
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1774474
Bug ID: 1774474
Summary: Missing some coverage in certain variants
Product: Fedora
Version: rawhide
Status: NEW
Component: dejavu-fonts
Severity: low
Assignee: nicolas.mailhot(a)laposte.net
Reporter: tagoh(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
nicolas.mailhot(a)laposte.net, paul(a)frixxon.co.uk,
peter(a)thecodergeek.com
Target Milestone: ---
Classification: Fedora
Description of problem:
I'm expecting to see same glyph coverage to all variants available in the
package but apparently not. this is just a result running some test cases with
fc-validate against languages which is expectedly or unexpectedly supposed to
assign dejavu as a default font for.
See logs stored in the following link for more details. that demonstrates this
issue.
https://jenkins-continuous-infra.apps.ci.centos.org/blue/rest/organizatio...
Version-Release number of selected component (if applicable):
2.37-2.fc31
How reproducible:
always
Steps to Reproduce:
1.fc-validate -l <lang> /path/to/fonts
2.
3.
Actual results:
(One of) snippet from logs:
[2019-11-19T14:20:10.928Z] RESULT: PASS:
/usr/share/fonts/dejavu/DejaVuSans-Bold.ttf satisfy ab language coverage.
[2019-11-19T14:20:10.928Z] RESULT: PASS:
/usr/share/fonts/dejavu/DejaVuSans.ttf satisfy ab language coverage.
[2019-11-19T14:20:10.928Z] RESULT: PASS:
/usr/share/fonts/dejavu/DejaVuSansCondensed-Oblique.ttf satisfy ab language
coverage.
[2019-11-19T14:20:10.928Z] RESULT: PASS:
/usr/share/fonts/dejavu/DejaVuSans-Oblique.ttf satisfy ab language coverage.
[2019-11-19T14:20:10.928Z] RESULT: FAIL:
/usr/share/fonts/dejavu/DejaVuSans-ExtraLight.ttf doesn't satisfy ab language
coverage.
[2019-11-19T14:20:10.928Z] RESULT: PASS:
/usr/share/fonts/dejavu/DejaVuSansCondensed-Bold.ttf satisfy ab language
coverage.
[2019-11-19T14:20:10.928Z] RESULT: PASS:
/usr/share/fonts/dejavu/DejaVuSansCondensed-BoldOblique.ttf satisfy ab language
coverage.
[2019-11-19T14:20:10.928Z] RESULT: PASS:
/usr/share/fonts/dejavu/DejaVuSansCondensed.ttf satisfy ab language coverage.
[2019-11-19T14:20:10.928Z] RESULT: PASS:
/usr/share/fonts/dejavu/DejaVuSans-BoldOblique.ttf satisfy ab language
coverage.
[2019-11-19T14:20:10.928Z] Run test ab: done. Test's exit code: 0
Expected results:
ExtraLight should have same coverage.
Additional info:
As it is an experimental, this may be an RFE.
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 11 months
[Bug 1813230] New: [RFE] ghostscript add support for variable fonts
from fontconfig
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1813230
Bug ID: 1813230
Summary: [RFE] ghostscript add support for variable fonts from
fontconfig
Product: Red Hat Enterprise Linux 8
Version: 8.4
Status: NEW
Component: ghostscript
Assignee: zdohnal(a)redhat.com
Reporter: zdohnal(a)redhat.com
QA Contact: qe-baseos-daemons(a)redhat.com
CC: cosimo.cecchi(a)gmail.com, dkaspar(a)redhat.com,
extras-qa(a)fedoraproject.org,
fonts-bugs(a)lists.fedoraproject.org, ian(a)ianweller.org,
jsteiner(a)redhat.com, klember(a)redhat.com, me(a)fale.io,
mosvald(a)redhat.com, tagoh(a)redhat.com,
twaugh(a)redhat.com, zdohnal(a)redhat.com
Depends On: 1813187
Target Milestone: rc
Classification: Red Hat
Pool ID: sst_cs_infra_services_rhel_8
+++ This bug was initially created as a clone of Bug #1813187 +++
Description of problem:
During investigating https://bugzilla.redhat.com/show_bug.cgi?id=1722900 was
found the font mentioned in summary fails with mismatch on
FcPatternGetInteger() from fontconfig when gs asks for FC_WEIGHT value.
I'm not sure whether the font or fontconfig is at fault, so I'm filing the
issue on font package.
I'm willing to help with debug, if needed.
Version-Release number of selected component (if applicable):
abattis-cantarell-fonts-0:0.201-2.fc32.noarch
fontconfig-2.13.92-6.fc32.x86_64
ghostscript-9.50-1.fc32
Steps to Reproduce:
1. gs -dNODISPLAY -dBATCH nasmdoc.ps
Actual results:
You can see in logs a message:
DEBUG: FC_WEIGHT didn't match in /usr/share/fonts/cantarell/Cantarell-VF.otf
Expected results:
No such message
Additional info:
--- Additional comment from Kalev Lember on 2020-03-13 08:32:41 UTC ---
Sorry, I don't know much about fonts and don't think I can be of much help
debugging this. Can you ask Jakub and/or Tagoh if they know what's going on
(CCd)?
--- Additional comment from Nicolas Mailhot on 2020-03-13 08:42:52 UTC ---
On the fontconfig side, that’s basically bug
https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/222
No idea if gs also contains problematic weight assumptions, invalidated by the
introduction of variable fonts.
On the packaging side cantarell has probably not been converted to new font
packaging guidelines yet. It needs some name fixing (use of a space-free
ExtraBold qualifier, removal of Regular in Name ID 4 for the Regular face,
making NameID 4 consistent with Name ID 17 for other faces). Though except for
the ExtraBold part, everything else will going to be workarounded in future
fontconfig versions.
--- Additional comment from Nicolas Mailhot on 2020-03-13 08:52:38 UTC ---
(Also fontconfig exposes a generic meta face for variable fonts, this face does
not have any specific weight, it gives the weight scale for the whole family)
--- Additional comment from Akira TAGOH on 2020-03-13 08:58:05 UTC ---
That isn't related to this.
I don't know how ghostscript collects fonts from fontconfig though (probably
using FcFontList()?), the problem here would be that they have dealt with a
meta face as a normal face which has true in FC_VARIABLE and contains a weight
in range but not integer.
That's not a bug in font nor fontconfig.
--- Additional comment from Zdenek Dohnal on 2020-03-13 09:25:03 UTC ---
Hi Akira,
yes, you're right, gs uses FcFontlist() - does the following to get font list:
-----------------------------------------------------
/* load the font set that we'll iterate over */
pat = FcPatternBuild(NULL,
FC_OUTLINE, FcTypeBool, 1,
FC_SCALABLE, FcTypeBool, 1,
NULL);
os = FcObjectSetBuild(FC_FILE, FC_OUTLINE,
FC_FAMILY, FC_WEIGHT, FC_SLANT,
NULL);
state->font_list = FcFontList(0, pat, os);
-----------------------------------------------------
then when it enumerates the fonts it calls (f.e. for FC_WEIGHT):
result = FcPatternGetInteger (font, FC_WEIGHT, 0, &weight_fc);
(similar thing for FC_FILE, FC_FAMILY, FC_SLANT, FC_OUTLINE).
Would you mind telling me/pointing me to a manual how to deal with it
correctly, if it is not a problem of font/fontconfig?
--- Additional comment from Akira TAGOH on 2020-03-13 10:07:42 UTC ---
If ghostscript has no plans to support variable fonts or a plan to support only
named-instances, you can set false to FC_VARIABLE
as a query pattern; that should be more simple and easier than your patch
applied in ghostscript; you can take care of the named-instances in VF font
files as same as usual face then. otherwise set FcDontCare to FC_VARIABLE and
need more changes in the code to deal with non-named-instances perhaps.
The meta face which you faced the issue this time provides such information
instead of providing it as one of faces because there are so many patterns to
enummerate everything and quite hard to do. the targetted properties such as
FC_WEIGHT, FC_WIDTH and FC_SIZE has a value in FcRange which means they can use
an unique value between them.
Unfortunately there are no more detailed document though, pango source code may
helps how to deal with them.
--- Additional comment from Akira TAGOH on 2020-03-13 10:16:22 UTC ---
You can see what values the meta face provides. try fc-list -b -v
Cantarell:variable=true for example.
--- Additional comment from Zdenek Dohnal on 2020-03-13 10:40:41 UTC ---
IMO they are not aware of the fact the variable fonts need a special care when
are used from fontconfig.
I'll check with upstream about variable fonts then.
Thank you for the info!
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1813187
[Bug 1813187] ghostscript does not load variable fonts from fontconfig
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 11 months
[Bug 1813187] New: Cantarell-VF.otf fails on fontconfig's
FcPatternGetInteger() call for FC_WEIGHT
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1813187
Bug ID: 1813187
Summary: Cantarell-VF.otf fails on fontconfig's
FcPatternGetInteger() call for FC_WEIGHT
Product: Fedora
Version: 32
Status: NEW
Component: abattis-cantarell-fonts
Assignee: klember(a)redhat.com
Reporter: zdohnal(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: cosimo.cecchi(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org, ian(a)ianweller.org,
klember(a)redhat.com, me(a)fale.io
Target Milestone: ---
Classification: Fedora
Description of problem:
During investigating https://bugzilla.redhat.com/show_bug.cgi?id=1722900 was
found the font mentioned in summary fails with mismatch on
FcPatternGetInteger() from fontconfig when gs asks for FC_WEIGHT value.
I'm not sure whether the font or fontconfig is at fault, so I'm filing the
issue on font package.
I'm willing to help with debug, if needed.
Version-Release number of selected component (if applicable):
abattis-cantarell-fonts-0:0.201-2.fc32.noarch
fontconfig-2.13.92-6.fc32.x86_64
ghostscript-9.50-1.fc32
Steps to Reproduce:
1. gs -dNODISPLAY -dBATCH nasmdoc.ps
Actual results:
You can see in logs a message:
DEBUG: FC_WEIGHT didn't match in /usr/share/fonts/cantarell/Cantarell-VF.otf
Expected results:
No such message
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 11 months
[Bug 1753295] New: Pango no longer supports bitmap fonts
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1753295
Bug ID: 1753295
Summary: Pango no longer supports bitmap fonts
Product: Fedora
Version: 31
Status: NEW
Component: pango
Assignee: tagoh(a)redhat.com
Reporter: jsbillin(a)umich.edu
QA Contact: extras-qa(a)fedoraproject.org
CC: 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, mclasen(a)redhat.com,
pwu(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com,
tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
In pango 1.44, pango dropped support for bitmap fonts, so font packages like
terminus-fonts and ucs-miscfixed-fonts no longer appear in GNOME applications
that use pango, such as Terminal. If you did a dnf system-upgrade from Fedora
30 and were using a bitmap font like Terminus, all your terminals will show the
rectangular placeholders the first time you start a terminal.
Bitmap fonts like terminus and ucs-miscfixed are much easier to read in a
terminal since they are pixel perfect. If Fedora 31 is going to disable
support for bitmap fonts, it needs to be announced and the package maintainers
of those bitmap font packages are going to need to find a way to convert their
fonts.
Version-Release number of selected component (if applicable):
pango-1.44.6-1.fc31.x86_64
How reproducible:
always
Steps to Reproduce:
1. install 'terminus-fonts'
2. Start GNOME terminal
3. Open Terminal Preferences
4. Attempt to change the font to Terminus font
Actual results:
If you upgraded from Fedora 30 and had Terminus fonts as the default font, the
first time you launch Terminal, all the text will be the rectangular
placeholders. If you search for the Terminus font in the preferences, you
won't be able to find it.
Expected results:
Use the Terminus font as usual
Additional info:
It appears that pango switched from using FreeType to HarfBuzz, which only
supports truetype. I rebuilt the Fedora 30 pango package (1.43) for Fedora 31,
downgraded it, and now my terminals are fine showing my bitmap fonts.
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 11 months
[Bug 1660284] New: IndexError: list index out of range
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1660284
Bug ID: 1660284
Summary: IndexError: list index out of range
Product: Fedora
Version: rawhide
Status: NEW
Component: fonttools
Assignee: pnemade(a)redhat.com
Reporter: tagoh(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
pnemade(a)redhat.com, sshedmak(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
/usr/bin/fonttools dumps a traceback when calling.
$ fonttools
Traceback (most recent call last):
File "/bin/fonttools", line 11, in <module>
load_entry_point('fonttools==3.32.0', 'console_scripts', 'fonttools')()
File "/usr/lib/python3.7/site-packages/fontTools/__main__.py", line 24, in
main
mod = 'fontTools.'+sys.argv[1]
IndexError: list index out of range
That would be better if that can shows more helpful usage or so.
Version-Release number of selected component (if applicable):
fonttools-3.32.0-1.fc30.noarch
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years
[Bug 1808064] New: Font-Awesome is not updated
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1808064
Bug ID: 1808064
Summary: Font-Awesome is not updated
Product: Fedora
Version: 31
Status: NEW
Component: fontawesome-fonts
Assignee: pvoborni(a)redhat.com
Reporter: tjamadeira(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org, mrunge(a)redhat.com,
pvoborni(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
The font-awesome it isn't updated.
What can be done about this?
How reproducible:
Always.
Steps to Reproduce:
1. Install font awesome via dnf
2. See the version of it.
Actual results:
Actual version is 4.7
Expected results:
Version 5.12
Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1543407
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 1 month
[Bug 1749943] New: pango contain header with wrong hb.h include
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1749943
Bug ID: 1749943
Summary: pango contain header with wrong hb.h include
Product: Fedora
Version: rawhide
Status: NEW
Component: pango
Assignee: tagoh(a)redhat.com
Reporter: vascom2(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: 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, mclasen(a)redhat.com,
pwu(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com,
tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
I am try to build eiskaltdcpp and it fsilrd with error:
BUILDSTDERR: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error:
hb.h: No such file or directory
BUILDSTDERR: 28 | #include <hb.h>
BUILDSTDERR: | ^~~~~~
Full build log
https://kojipkgs.fedoraproject.org/work/tasks/5226/37235226/build.log
Version-Release number of selected component (if applicable):
pango-1.44.6-1.fc32
How reproducible:
Always.
As I see this line was added in pango 1.44. But harfbuzz's hb.h in Fedora
placed at /usr/include/harfbuzz/
Need to solve it for build other packages.
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 1 month