[Bug 1068918] New: Google Droid Sans font is displayed as [unknown] and [monotype], it breaks GTK+ apps view in KDE
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1068918
Bug ID: 1068918
Summary: Google Droid Sans font is displayed as [unknown] and
[monotype], it breaks GTK+ apps view in KDE
Product: Fedora
Version: 20
Component: google-droid-fonts
Assignee: nicolas.mailhot(a)laposte.net
Reporter: carasin.berlogue(a)mail.ru
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
hobbes1069(a)gmail.com, nicolas.mailhot(a)laposte.net,
paul(a)frixxon.co.uk, tremble(a)tremble.org.uk
External Bug ID: Red Hat Bugzilla 963502
Description of problem:
>
[google-droid-sans-fonts] package is broken since F18. I want to select 'Droid
Sans' font for KDE UI, but this font is displayed twice at [systemsettings]:
with [unknown] and [monotype] suffixes. If I apply anyone of them, only KDE/Qt
apps use 'Droid Sans' font, but GTK2/GTK3 apps use the defaul font (DejaVu
Sans).
Version-Release number of selected component (if applicable):
>
google-droid-sans-fonts-20120715-6.fc20.noarch
How reproducible:
>
Always.
Steps to Reproduce:
>
1. [yum install google-droid-sans-fonts];
2. start KDE session;
3. launch <select UI fonts> dialog at [systemsettings];
4. 'Droid Sans' font is displayed twice: with [unknown] and [monotype]
suffixes;
5. select and apply anyone — 'Droid Sans [unknown]' or 'Droid Sans [monotype]';
6. KDE/Qt apps use the Droid Sans font, but GTK2/GTK3 apps use the defaul font
(DejaVu Sans).
Actual results:
>
'Droid Sans' font is not applied for GTK2/GTK3 apps. This font is displayed
twice at [systemsettings]: with [unknown] and [monotype] suffixes.
Expected results:
>
'Droid Sans' font is applied for all the apps. This font is displayed once at
[systemsettings] — without any suffix.
Additional info:
>
This bug is several years old.
https://bugzilla.redhat.com/show_bug.cgi?id=963502#c1
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=EIzrPE5DPR&a=cc_unsubscribe
7 years, 9 months
[Bug 1169979] New: Some fonts not in fontconfig cache on Fedora 21 live images
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1169979
Bug ID: 1169979
Summary: Some fonts not in fontconfig cache on Fedora 21 live
images
Product: Fedora
Version: 21
Component: fontconfig
Assignee: tagoh(a)redhat.com
Reporter: awilliam(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, pnemade(a)redhat.com,
tagoh(a)redhat.com
We've spotted an issue with Fedora 21 live images where some installed fonts
appear to be missing from the fontconfig cache in the live environment. An
'fc-cache -f' fixes this. For instance, on the Fedora 21 Final RC2 Workstation
x86_64 live:
[root@localhost liveuser]# fc-list | wc -l
141
[root@localhost liveuser]# fc-cache --force
[root@localhost liveuser]# fc-list | wc -l
159
The specific fonts that are missing on that image are:
/usr/share/fonts/dejavu/DejaVuSansMono-BoldOblique.ttf: DejaVu Sans
Mono:style=Bold Oblique
/usr/share/fonts/dejavu/DejaVuSansMono-Bold.ttf: DejaVu Sans Mono:style=Bold
/usr/share/fonts/dejavu/DejaVuSansMono-Oblique.ttf: DejaVu Sans
Mono:style=Oblique
/usr/share/fonts/dejavu/DejaVuSansMono.ttf: DejaVu Sans Mono:style=Book
/usr/share/fonts/dejavu/DejaVuSerif-BoldItalic.ttf: DejaVu Serif:style=Bold
Italic
/usr/share/fonts/dejavu/DejaVuSerif-Bold.ttf: DejaVu Serif:style=Bold
/usr/share/fonts/dejavu/DejaVuSerifCondensed-BoldItalic.ttf: DejaVu
Serif,DejaVu Serif Condensed:style=Condensed Bold Italic,Bold Italic
/usr/share/fonts/dejavu/DejaVuSerifCondensed.ttf: DejaVu Serif,DejaVu Serif
Condensed:style=Condensed,Book
/usr/share/fonts/dejavu/DejaVuSerif-Italic.ttf: DejaVu Serif:style=Italic
/usr/share/fonts/dejavu/DejaVuSerif.ttf: DejaVu Serif:style=Book
/usr/share/fonts/google-noto/NotoSansTagalog-Regular.ttf: Noto Sans
Tagalog:style=Regular
/usr/share/fonts/google-noto/NotoSansTaiViet-Regular.ttf: Noto Sans Tai
Viet:style=Regular
/usr/share/fonts/liberation/LiberationSerif-BoldItalic.ttf: Liberation
Serif:style=Bold Italic
/usr/share/fonts/liberation/LiberationSerif-Bold.ttf: Liberation
Serif:style=Bold
/usr/share/fonts/liberation/LiberationSerif-Italic.ttf: Liberation
Serif:style=Italic
/usr/share/fonts/liberation/LiberationSerif-Regular.ttf: Liberation
Serif:style=Regular
The log of the compose is here:
https://kojipkgs.fedoraproject.org//work/tasks/5463/8275463/root.log
In comparison, the i686 Workstation live is 'missing' only
/usr/share/fonts/google-noto/NotoSansTaiViet-Regular.ttf: Noto Sans Tai
Viet:style=Regular
its compose log is here:
https://kojipkgs.fedoraproject.org//work/tasks/5460/8275460/root.log
to me, it appears the affected cases are ones where more than one package
contains fonts in the same directory, for packages installed *after* the
fontconfig package. The fontconfig package has an 'fc-cache -f' in its %post,
so any inconsistencies that exist before it's installed get fixed by that.
My first thesis was 'for any given directory, only fonts from the first package
installed after fontconfig will make it to the cache, fonts in the same
directory from subsequently-installed packages won't be added'. But it doesn't
seem to be that simple, because some fonts in /usr/share/fonts/google-noto
*are* added - the first 'noto' package installed is google-noto-sans-lisu-fonts
, and after that several more noto packages are installed. The fonts from
google-noto-sans-mandaic-fonts, google-noto-sans-meeteimayek-fonts , and
google-noto-sans-tai-tham-fonts *do* get added to the cache - but the fonts
from google-noto-sans-tagalog-fonts and google-noto-sans-tai-viet-fonts do
*not* get added. It's quite odd.
This is a fairly bad bug because of its impact on DejaVu Sans Mono: this is the
default monospace font for both Workstation and KDE (and I think the
non-blocking spins too). Its absence from the cache results in them using
Nimbus Mono L as their monospace fonts, which is a pretty crappy font, ugly and
hard to read. The workaround is easy once you know it, but if you don't, you
just think we have a really bad font.
There's an easy big hammer workaround we can use for a quick rebuild of the RC2
lives, if we like:
--- a/fedora-live-base.ks
+++ b/fedora-live-base.ks
@@ -299,6 +299,12 @@ rm -f /core*
# convince readahead not to collect
# FIXME: for systemd
+# forcibly regenerate fontconfig cache (so long as this live image has
+# fontconfig) - see #XXXXXXX
+if [ -x /usr/bin/fc-cache ] ; then
+ fc-cache -f
+fi
+
%end
i.e., just do an fc-cache -f at the end of live generation %post. I've tested
that locally, and it works, the generated Workstation image has 159 fonts in
fc-list (I also generated an image with the exact same config and build host,
but no change to spin-kickstarts, to verify that it reproduced the bug, and it
does).
The real fix should likely be in fc-cache, but the spin-kickstarts workaround
would solve this problem for F21.
I think fc-cache's behaviour must have changed between F20 and F21, as F20
doesn't appear to be affected by this at all, at least not the x86_64 desktop
live. All F21 images I've tested seem to be affected to some extent, though the
exact affected fonts vary depending on the package install order that yum
decided on.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=YTmueYxE1e&a=cc_unsubscribe
7 years, 10 months
[Bug 527740] New: [ml_IN] Applying Backspace to a chillu conjunct followed by punctuation/SPACE results in deletion of the chillu also
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: [ml_IN] Applying Backspace to a chillu conjunct followed by punctuation/SPACE results in deletion of the chillu also
https://bugzilla.redhat.com/show_bug.cgi?id=527740
Summary: [ml_IN] Applying Backspace to a chillu conjunct
followed by punctuation/SPACE results in deletion of
the chillu also
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Keywords: i18n
Severity: medium
Priority: low
Component: pango
AssignedTo: besfahbo(a)redhat.com
ReportedBy: apeter(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: eng-i18n-bugs(a)redhat.com, besfahbo(a)redhat.com,
fedora-fonts-bugs-list(a)redhat.com,
smc-discuss(a)googlegroups.com
Classification: Fedora
Target Release: ---
Created an attachment (id=363982)
--> (https://bugzilla.redhat.com/attachment.cgi?id=363982)
Screenshot for chillu conjuncts
Description of problem:
When chillu conjuncts are followed by any punctuation marks like "!", ".", ",",
"'", "?" or SPACE, ie when a word ends with a chillu conjunct, and followed by
a punctuation mark or a SPACE, using Backspace to delete the punctuation mark
or SPACE results in the deletion of chillu conjunct together with the
punctuation mark/SPACE.
Version-Release number of selected component (if applicable):
pango 1.26.0-1.fc12 i686
How reproducible:
Always
Steps to Reproduce:
1. Open gedit
2. type any of chillu conjunct, eg: 0D28, 0D4D, 200D
OR
type a word ending with chillu conjunct, eg: 0D05, 0D35, 0D28, 0D4D, 200D
3. type any punctuation marks like "!", ".", ",", "'", "?" or SPACE
4. Press Backspace
Actual results:
When using Backspace after chillu conjunct followed by punctuation mark or
SPACE, instead of deleting punctuation mark or SPACE only, the chillu conjunct
also gets deleted.
Expected results:
When using Backspace after chillu conjunct followed by punctuation mark or
SPACE, only the punctuation mark/SPACE should get deleted.
Additional info:
1. This does not happen when chillu comes in between a word. eg: നന്മ (0D28,
0D28, 0D4D, 200D, 0D2E)
2. This issue is not present in oowriter and kwrite. When above steps are
reproduced, deletions happens in correct order.
Versions used:
libicu-4.2.1-6.fc12 i686
qt-4.5.2-22.fc12 i686
3. Screenshot attached for chillu conjuncts and eg of words with chillu
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
7 years, 11 months
[Bug 1206752] New: [abrt] fonttools: subset.py:2282:_closure_glyphs:MissingGlyphsSubsettingError: set(['./Apps/msfinal/public/textos/index.html'])
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1206752
Bug ID: 1206752
Summary: [abrt] fonttools:
subset.py:2282:_closure_glyphs:MissingGlyphsSubsetting
Error:
set(['./Apps/msfinal/public/textos/index.html'])
Product: Fedora
Version: 22
Component: fonttools
Assignee: pnemade(a)redhat.com
Reporter: diogocamposwd(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org, pnemade(a)redhat.com
Version-Release number of selected component:
fonttools-2.5-2.fc22
Additional info:
reporter: libreport-2.5.0
cmdline: /usr/bin/python2 /usr/bin/pyftsubset
./Downloads/Sintony-Regular.ttf ./Apps/msfinal/public/textos/index.html
executable: /usr/bin/pyftsubset
kernel: 4.0.0-0.rc4.git0.1.fc22.x86_64
runlevel: unknown
type: Python
uid: 1000
Truncated backtrace:
#1 _closure_glyphs in
/usr/lib/python2.7/site-packages/FontTools/fontTools/subset.py:2282
#2 subset in
/usr/lib/python2.7/site-packages/FontTools/fontTools/subset.py:2387
#3 main in /usr/lib/python2.7/site-packages/FontTools/fontTools/subset.py:2602
#4 <module> in /usr/bin/pyftsubset:6
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=aMgosC2dVM&a=cc_unsubscribe
8 years
[Bug 1240265] New: fonttools 2.5 takes too much memory
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1240265
Bug ID: 1240265
Summary: fonttools 2.5 takes too much memory
Product: Fedora
Version: 22
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
Description of problem:
related to Bug#1239985, after upgrading fonttools to 2.5, it doesn't work
anymore to decompile ttf to ttx.
Version-Release number of selected component (if applicable):
2.5-2.fc22
How reproducible:
always
Steps to Reproduce:
1.ttx -a -i -e sazanami-gothic.ttf
2.
3.
Actual results:
OOM killer kills the process
Expected results:
should works as it worked before.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Zdw8HK8hNu&a=cc_unsubscribe
8 years
[Bug 507292] New: [RFE] Allow wildcards/regexps in rpm deps
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: [RFE] Allow wildcards/regexps in rpm deps
https://bugzilla.redhat.com/show_bug.cgi?id=507292
Summary: [RFE] Allow wildcards/regexps in rpm deps
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: rpm
AssignedTo: pmatilai(a)redhat.com
ReportedBy: nicolas.mailhot(a)laposte.net
QAContact: extras-qa(a)fedoraproject.org
CC: pmatilai(a)redhat.com, jnovy(a)redhat.com,
ffesti(a)redhat.com, fedora-fonts-bugs-list(a)redhat.com
Classification: Fedora
(this is mostly a yum-level RFE, but it would be nice if we kept the same
depsolving logic in both apps)
The problem:
Selecting a font is a multi-criterium operation. We need to match on font
family, font style, language support, unicode support, etc. At any time all of
just some of those selection criterii can be provided by the user or
applications.
To have features like font auto-installation work reliably, this matching needs
to extend to the package database
Right now rpm is only allowing to specify atomic provides, so we can have a
font package that
Provides font(dejavusans)
and
Provides
font(:lang=el)
but there is no warranty both those provides are belonging to the same font.
There is no way to distinguish between a package that includes an actual greek
dejavusans and a package that includes a dejavusans greek-less file and another
totally different greek font
To workaround this rpm limitation we've been asking packagers to put font files
belonging to different font families in different packages. However:
1. many still don't
2. it's not technically possible for all font formats, for example the ttc font
format allows mixing of fonts with different characteristics in a single file
The ideal solution:
Ability to have Provides like:
font(comma-separated font name list|comma-separated style list|comma-separated
lang list) (rough mockup that probably needs refining)
And have deps like (dejavu|*|el) work in rpm
(yes a font can declare many different names, be available in many different
styles, cover many different languages)
For ttc files we'd then generate one Provides for each font included in the ttc
bundle
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
8 years, 1 month
[Bug 1227614] New: Font rendering is poor in Fedora 22
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1227614
Bug ID: 1227614
Summary: Font rendering is poor in Fedora 22
Product: Fedora
Version: 22
Component: freetype
Assignee: mkasik(a)redhat.com
Reporter: sudhir(a)sudhirkhanger.com
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
Created attachment 1034149
--> https://bugzilla.redhat.com/attachment.cgi?id=1034149&action=edit
screenshot
Description of problem:
Font rendering on Fedora 21 KDE worked fine. But in Fedora 22 which uses
freetype-2.5.5-1.fc22.x86_64 it is way too grainier. I use slight hint which
doesn't seem to be applied at all. RPMFusion which uses F21's
freetype-freeworld-2.3.11 works fine. So something must have gone wrong in the
update.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=aU8lA46g7B&a=cc_unsubscribe
8 years, 4 months
[Bug 1195021] New: The ttf oldstandard-sfd fonts are corrupted
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1195021
Bug ID: 1195021
Summary: The ttf oldstandard-sfd fonts are corrupted
Product: Fedora
Version: 20
Component: oldstandard-sfd-fonts
Assignee: sanjay.ankur(a)gmail.com
Reporter: eko(a)lanet.lv
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
sanjay.ankur(a)gmail.com
Created attachment 994206
--> https://bugzilla.redhat.com/attachment.cgi?id=994206&action=edit
An exmple of errors in the ttf file.
Description of problem:
The ttf files are with errors.
Version-Release number of selected component (if applicable):
oldstandard-sfd-fonts-2.0.2-13.fc20
The same with oldstandard-sfd-fonts-2.0.2-15.fc21. The corrupted fonts has a
very long history – the ttf files from package
oldstandard-sfd-fonts-2.0.2-3.fc10 are already damaged.
How reproducible:
100%
Steps to Reproduce:
1. Open /usr/share/fonts/oldstandard/* files with any font viewer.
Actual results:
There is a garbage in place of letters (see the attached screen-shot)
Expected results:
Usable fonts.
Additional info:
I try to rebuilt this package from SRPM – no luck. The fontforge refuses to
built usable ttf even by hand. There are two options to solve the issue:
1) To generate OTF not the TTF (preferred solution);
2) To use ready-made ttf from
http://www.fontsquirrel.com/fonts/old-standard-TT.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=0XRZ2KCY22&a=cc_unsubscribe
8 years, 4 months