[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
--- Comment #46 from Hans Ulrich Niedermann <rhbugs(a)n-dimensional.de> ---
For experimenting, I have created a copr with terminus-fonts-4.48-2.fc31.1.3 at
https://copr.fedorainfracloud.org/coprs/ndim/otb-bitmap-fonts/packages/.
As you can see at
https://copr-be.cloud.fedoraproject.org/results/ndim/otb-bitmap-fonts/fed...,
this means there are now three separate packages to experiment with:
terminus-fonts
containing the convertfont.py/fonttosfnt generated
/usr/share/fonts/terminus/TerminusBold.otb
/usr/share/fonts/terminus/TerminusRegular.otb
and the mkfontdir generated
/usr/share/fonts/terminus/fonts.dir
(is this still required for OpenType fonts?)
terminus-fonts-legacy-bdf
Contains the original bdf files as shipped from terminus-font upstream.
This works e.g. with the emacs Xft font backend.
/usr/share/fonts/terminus-legacy-bdf/fonts.dir
/usr/share/fonts/terminus-legacy-bdf/ter-u12b.bdf
/usr/share/fonts/terminus-legacy-bdf/ter-u12n.bdf
and a good dozen of bdf files
terminus-fonts-legacy-pcf
Contains the *.pcf.gz files as built by upstream terminus-font.
This works e.g. with the emacs Xft font backend.
/etc/X11/fontpath.d/terminus:unscaled ->
/usr/share/fonts/terminus-legacy-pcf
/usr/share/fonts/terminus-legacy-pcf/fonts.dir
/usr/share/fonts/terminus-legacy-pcf/ter-112b.pcf.gz
/usr/share/fonts/terminus-legacy-pcf/ter-112n.pcf.gz
plus about 250 more ter-*.pcf.gz files
Some entries in the respective fonts.dir files are the same, but pointing to a
different font file.
As it turns out, the botched invented "Terminus Italic" (probably invented by
fontconfig) consisting only of hex number in rectangle glyphs (what is the
proper term for those btw?) only appears in the gnome-terminal font selection
dialog when either the BDF or the PCF or both BDF and PCF fonts are installed.
However, there are applications which do not support OTB fonts yet. Not every
piece of Linux software in the world uses pango/harfbuzz. So removing the PCF
fonts (or even the BDF fonts which the terminus-fonts package had never
provided in the past) would remove an ABI on which software relies.
Some of that non-harfbuzz or pre-harfbuzz Linux software comes from the Fedora
set of packages, and some will come from outside Fedora. Providing those older
font formats as a compatibility layer for running that software certainly is
not the worst of ideas.
E.g. emacs upstream is still working on adding a harfbuzz font backend which
appears to be aimed for emacs 27, which has not been released yet, and that is
an important use case for e.g. Terminus.
As it stands, having more than *.otb causes the weird hex number rectangle
glyph "Terminus Italic", but not having *.bdf or *.pcf.gz breaks emacs for me,
so the hex number rectangle glyphs are the price to pay for that. As to other
more test cases than just gnome-terminal and emacs, I still need to look for
and test a number of those.
--
You are receiving this mail because:
You are on the CC list for the bug.
4 years, 3 months
[Bug 1784630] New: Source Sans Pro fonts should be upgraded to
version 3.006
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1784630
Bug ID: 1784630
Summary: Source Sans Pro fonts should be upgraded to version
3.006
Product: Fedora
Version: 31
Status: NEW
Component: adobe-source-sans-pro-fonts
Assignee: pikachu.2014(a)gmail.com
Reporter: agusbou2018(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: alexis.lameire(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
pikachu.2014(a)gmail.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Source Sans Pro fonts currently distributed on Fedora is the version 2.045.
They should be upgraded to version 3.006 (see
https://github.com/adobe-fonts/source-sans-pro).
Version-Release number of selected component (if applicable):
2.045-1.fc31
How reproducible:
always
Steps to Reproduce:
None.
Actual results:
Source Sans Pro fonts distributed on Fedora is the version 2.045
Expected results:
Source Sans Pro fonts should be upgraded to version 3.006
Additional info:
None.
--
You are receiving this mail because:
You are on the CC list for the bug.
4 years, 3 months
[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
Nicolas Mailhot <nicolas.mailhot(a)laposte.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tagoh(a)redhat.com
--- Comment #42 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> ---
(In reply to Hans Ulrich Niedermann from comment #38)
> Uhm. This is confusing. The font list for gnome-terminal starts with
>
> DejaVu Sans Mono Bold
> DejaVu Sans Mono Book
> DejaVu Sans Mono Oblique
> DejaVu Sans Mono Bold Oblique
> Droid Sans Mono Regular
> Droid Sans Mono Italic
> Droid Sans Mono Bold
> Droid Sans Mono Bold Italic
Well none of those exist in the font file themselves. (the giveaway is “DejaVu
Sans Mono Book” or “Droid Sans Mono Regular”)
The gnome-terminal font selector is reconstructing a fake Name ID 4 (aka
fullname) by collating Family (Name ID 16 or 21) and Style (Name ID 17 or 22).
Probably to workaround the following fontconfig bug:
https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/208
However, because the people that wrote the workaround did not bother reporting
their problem fonconfig-side, and because they didn’t bother reading the
OpenType Naming spec, they forgot the “Regular” special case. And the result is
no better than using raw Name ID 4 directly (which is broken for some
real-world font files).
You can check the actual metadata contained in font files with fontforge or
fc-scan (the later will apply fontconfig-level naming fixups)
--
You are receiving this mail because:
You are on the CC list for the bug.
4 years, 3 months