[Bug 1823637] Terminus fonts broken after
terminus-fonts-4.48-5.fc32.noarch update
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1823637
--- Comment #8 from Hans Ulrich Niedermann <rhbugs(a)n-dimensional.de> ---
I have updated my F31 system to F32 yesterday specifically for reproducing this
issue. However, my gnome-terminal font selection dialog behaves exactly the
same on F32 as it did on F31. It shows four font variants, two of which are
actually provided by the terminus-fonts package, and two of which are invented
by the fonts software stack for some reason:
Terminus Medium
Terminus Bold
<series of unicode hex code glyphs>
Terminus Bold Italic
Anyway, the reporter of this bug is showing something *very* different: His
gnome-terminal font selection dialog shows four apparent font variants in a
very diffent way:
<series of rectangles>
<series of rectangles>
<series of unicode hex code glyphs>
<series of rectangles>
(BTW, I am still looking for the proper term for those unicode hex code glyphs.
If you know that term, please let me know.)
I have removed the terminus-fonts package, and automagically the gnome-terminal
terminal and the gnome-terminal font selection dialog have changed to stop
including terminus. After re-installing the terminus-fonts package, both have
automagically started showing terminus fonts again. This behaviour is the same
both with the older terminus-fonts-4.48-3.fc32.noarch package (with
updates-testing disabled) and (with updates-testing enabled) the newer
terminus-fonts-4.48-5.fc32.noarch package.
I interpret this as the font installation and removal working very well and as
intended, and that ostree is messing up those automagical updates to the state
of the font set. So it looks as if ostree/fontconfig or something along those
lines is responsible for the reporter's issue and I cannot see what the
terminus-fonts package could do about this.
So either this bug needs to be address by ostree/fontconfig/something or I just
close it for terminus-fonts.
That the fonts software stack insists on inventing a broken italic version of a
font which explicitly choses not to ship an italic version is an *entirely*
*different* *issue*, and not the topic of this bug.
However, nobody needs to select those broken italic version from the font
selection box, as the fonts actually provided by terminus-fonts are in perfect
working order. The user experience is certainly better if you install
"terminus-fonts" if you want to use the Terminus font inside, say, your
gnome-terminal and emacs, and just ignore the obviously broken italic font
variant. The alternative is a separate package with legacy fonts for Emacs, and
the user having to find out about actually needing the legacy variant package,
then installing that legacy variant package in addition to the standard one to
have Terminus for both gnome-terminal and Emacs, and then they see the broken
italic font variants in the gnome-terminal font selection dialog again.
--
You are receiving this mail because:
You are on the CC list for the bug.
4 years
[Bug 1814349] Rename Request: google-caladea-fonts - Caladea, a
serif font family metric-compatible with Cambria font family
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1814349
Nicolas Mailhot <nicolas.mailhot(a)laposte.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|fedora-review? |fedora-review+
--- Comment #9 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> ---
You can probably remove the following line, looks like a cut & paste leftover
%global fontsex fonts/otf/*SC*otf
And given the description, maybe some Cambo aliasing would be in order (seems
Caladea is the same design, tweaked to fit into Cambria metrics
But, this is fine tuning. The spec works fine and we have a real active
upstream for the font family at last
APPROVED
--
You are receiving this mail because:
You are on the CC list for the bug.
4 years
[Bug 1748495] The terminus font is no longer found by gvim, so text
files come up with glyphs instead of characters.
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1748495
Fedora Update System <updates(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ON_QA |CLOSED
Fixed In Version|terminus-fonts-4.48-2.fc31 |terminus-fonts-4.48-2.fc31
| |terminus-fonts-4.48-5.fc32
Resolution|--- |ERRATA
Last Closed|2020-01-05 00:41:03 |2020-04-25 02:18:58
--- Comment #51 from Fedora Update System <updates(a)fedoraproject.org> ---
FEDORA-2020-7c418e8b13 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.
--
You are receiving this mail because:
You are on the CC list for the bug.
4 years
[Bug 1814349] Rename Request: google-caladea-fonts - Caladea, a
serif font family metric-compatible with Cambria font family
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1814349
--- Comment #7 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> ---
Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.zgK8wx
+ umask 022
+ cd /builddir/build/BUILD
+ cd Caladea-336a529cfad3d103d6527752686f8331d13e820a
+ grep -E '^"/usr/share/fontconfig/conf.avail/.+\.conf"'
/builddir/build/BUILD/Caladea-336a529cfad3d103d6527752686f8331d13e820a/ht-caladea-fonts.list
+ xargs '-I{}' -- sh -c 'xmllint --loaddtd --valid --nonet
'\''/builddir/build/BUILDROOT/ht-caladea-fonts-1.001-1.0.20200401git336a529.fc33.mng.x86_64{}'\''
>/dev/null && echo
/builddir/build/BUILDROOT/ht-caladea-fonts-1.001-1.0.20200401git336a529.fc33.mng.x86_64{}:
OK'
/builddir/build/BUILDROOT/ht-caladea-fonts-1.001-1.0.20200401git336a529.fc33.mng.x86_64/usr/share/fontconfig/conf.avail/30-0-ht-caladea-fonts.conf:2:
warning: failed to load external entity
"/builddir/build/BUILDROOT/ht-caladea-fonts-1.001-1.0.20200401git336a529.fc33.mng.x86_64/usr/share/fontconfig/fonts.dtd"
<!DOCTYPE fontconfig SYSTEM "../fonts.dtd">
^
/builddir/build/BUILDROOT/ht-caladea-fonts-1.001-1.0.20200401git336a529.fc33.mng.x86_64/usr/share/fontconfig/conf.avail/30-0-ht-caladea-fonts.conf:3:
validity error : Validation failed: no DTD found !
<fontconfig>
^
/builddir/build/BUILDROOT/ht-caladea-fonts-1.001-1.0.20200401git336a529.fc33.mng.x86_64/usr/share/fontconfig/conf.avail/62-ht-caladea-fonts.conf:2:
warning: failed to load external entity
"/builddir/build/BUILDROOT/ht-caladea-fonts-1.001-1.0.20200401git336a529.fc33.mng.x86_64/usr/share/fontconfig/fonts.dtd"
<!DOCTYPE fontconfig SYSTEM "../fonts.dtd">
^
/builddir/build/BUILDROOT/ht-caladea-fonts-1.001-1.0.20200401git336a529.fc33.mng.x86_64/usr/share/fontconfig/conf.avail/62-ht-caladea-fonts.conf:3:
validity error : Validation failed: no DTD found !
<fontconfig>
^
error: Bad exit status from /var/tmp/rpm-tmp.zgK8wx (%check)
Bad exit status from /var/tmp/rpm-tmp.zgK8wx (%check)
You need to fix your DTD declaration. See also
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
(sorry about this, it was not possible to validate all fontconfig files by
default with the previous macro system)
--
You are receiving this mail because:
You are on the CC list for the bug.
4 years