fonts-bugs January 2020

fonts-bugs@lists.fedoraproject.org

1 participants
62 discussions

[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 03 Jan '20

03 Jan '20

https://bugzilla.redhat.com/show_bug.cgi?id=1748495 --- Comment #39 from Hans Ulrich Niedermann <rhbugs(a)n-dimensional.de> --- Created attachment 1649541 --> https://bugzilla.redhat.com/attachment.cgi?id=1649541&action=edit emacs showing proper spacing in Gnome/Wayland session with PCF files Proper character spacing with PCF files. $ rpm -q emacs freetype harfbuzz pango terminus-fonts{,-legacy-x11} | grep -v i686 emacs-26.3-1.fc31.x86_64 freetype-2.10.0-3.fc31.x86_64 harfbuzz-2.6.1-2.fc31.x86_64 pango-1.44.7-1.fc31.x86_64 terminus-fonts-4.48-2.fc31.1.noarch terminus-fonts-legacy-x11-4.48-2.fc31.1.noarch $ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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 03 Jan '20

03 Jan '20

https://bugzilla.redhat.com/show_bug.cgi?id=1748495 --- Comment #38 from Hans Ulrich Niedermann <rhbugs(a)n-dimensional.de> --- (In reply to Nicolas Mailhot from comment #37) > (In reply to Hans Ulrich Niedermann from comment #36) > > I just noticed in the gnome-terminal font selection dialog, that > > instead of the expected fonts > > > > Terminus Bold > > Terminus Medium > > > > it also lists > > > > [Terminus Medium] in numeric glyphs > > Terminus Bold Italic > > it should only list one font, Terminus, with lots of styles (Regular, > Medium, Bold, Bold Italic, etc) > > However, that’s not an unexpected result of conversion from a legacy format. 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 ... All of those are *.ttf fonts, which is definitively not a legacy bitmap format: $ ls /usr/share/fonts/{google-droid,dejavu}/*Mono* /usr/share/fonts/dejavu/DejaVuSansMono-BoldOblique.ttf /usr/share/fonts/dejavu/DejaVuSansMono-Bold.ttf /usr/share/fonts/dejavu/DejaVuSansMono-Oblique.ttf /usr/share/fonts/dejavu/DejaVuSansMono.ttf /usr/share/fonts/google-droid/DroidSansMono.ttf $ Also, the gnome-terminal or gedit font selection dialogs do not allow selecting any styles of a single font, so listing each font in a number of styles appears to be just their way to show font styles. > Legacy formats have very poor (everything, but especially) naming support. > Converting to SFNT will usually involve fixing the naming layer (Name ID > 16/17, using WWS rules, and Name ID 4, as Family + Style except for regular > for which is named Family not family Regular). > > That’s probably something that could be scripted using fontforge’s python > bindings. Ah. As it turns out, if I split off the ter-*.pcf.gz files into a -legacy-x11 subpackage and only install the ter-*.otb files, the gnome-terminal font selection list will properly display the "Terminus Italic" font without any hex glyphs. However, not installing the ter-*.pcf.gz files will result in xlsfonts not listing any terminus fonts, and without ter-*.pcf.gz emacs will then start to have all weird character spacing. More trial and error to follow. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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 03 Jan '20

03 Jan '20

https://bugzilla.redhat.com/show_bug.cgi?id=1748495 --- Comment #37 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> --- (In reply to Hans Ulrich Niedermann from comment #36) > I just noticed in the gnome-terminal font selection dialog, that > instead of the expected fonts > > Terminus Bold > Terminus Medium > > it also lists > > [Terminus Medium] in numeric glyphs > Terminus Bold Italic it should only list one font, Terminus, with lots of styles (Regular, Medium, Bold, Bold Italic, etc) However, that’s not an unexpected result of conversion from a legacy format. Legacy formats have very poor (everything, but especially) naming support. Converting to SFNT will usually involve fixing the naming layer (Name ID 16/17, using WWS rules, and Name ID 4, as Family + Style except for regular for which is named Family not family Regular). That’s probably something that could be scripted using fontforge’s python bindings. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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 03 Jan '20

03 Jan '20

https://bugzilla.redhat.com/show_bug.cgi?id=1748495 --- Comment #36 from Hans Ulrich Niedermann <rhbugs(a)n-dimensional.de> --- I just noticed in the gnome-terminal font selection dialog, that instead of the expected fonts Terminus Bold Terminus Medium it also lists [Terminus Medium] in numeric glyphs Terminus Bold Italic The [Terminus Medium] in the numeric glyphs probably should be "Terminus Medium Italic" according to whatever piece of software which has invented these italic versions of Terminus Medium and Terminus Bold. I have no idea which piece of software invents these italic versions. It might be fontforge during the bdf to otb conversion, it might be pango/harfbuzz, or it might be something else. In any case, the invented [Terminus Medium] in numeric glyphs font causes numeric glyphs to be rendered. I hope I can find a flag I change in the font files somewhere to prevent the invention of those two italic font variations. Package versions in use: $ rpm -q harfbuzz pango gnome-terminal terminus-fonts fontforge | grep -v i686 | sort fontforge-20190801-1.fc31.x86_64 gnome-terminal-3.34.2-1.fc31.x86_64 harfbuzz-2.6.1-2.fc31.x86_64 pango-1.44.7-1.fc31.x86_64 terminus-fonts-4.48-1.fc31.3.noarch $ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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 03 Jan '20

03 Jan '20

https://bugzilla.redhat.com/show_bug.cgi?id=1748495 --- Comment #35 from Jan Pazdziora <jpazdziora(a)redhat.com> --- With terminus-fonts-4.48-2.fc31.noarch, Terminus Medium 8 fonts works fine for me with xfce4-terminal-0.8.8-2.fc31.x86_64 and pango-1.44.7-1.fc31.x86_64. Thank you. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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 03 Jan '20

03 Jan '20

https://bugzilla.redhat.com/show_bug.cgi?id=1748495 --- Comment #34 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> --- > Now I am trying to read the current font guidelines, to fish out the > information applying for bitmap fonts from amongst instructions using > tools not shipped in Fedora at all (ttname), applying to vector fonts > only, etc. The current font packaging policy has been badly mangled during (botched) conversion to asciidoc, end never contained a lot of bitmap instructions If you want to work in the guidelines space, start from https://pagure.io/packaging-committee/pull-request/934 that's the version FPC is working on now. (further PRs are welcome) Alternatively, read the old policy in its archived wiki version, you won’t miss all the parts the asciidoc script dropped. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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 03 Jan '20

03 Jan '20

https://bugzilla.redhat.com/show_bug.cgi?id=1748495 Fedora Update System <updates(a)fedoraproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |MODIFIED --- Comment #33 from Fedora Update System <updates(a)fedoraproject.org> --- FEDORA-2020-619cd50145 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-619cd50145 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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 03 Jan '20

03 Jan '20

https://bugzilla.redhat.com/show_bug.cgi?id=1748495 --- Comment #32 from Hans Ulrich Niedermann <rhbugs(a)n-dimensional.de> --- Font selection in gnome-terminal does not appear to be a problem here even with many ter-u*b.otb and ter-u*n.otb files in /usr/share/fonts/terminus. So at least for now, I will be going the fontforge route for OTB, and keep the old *.pcf.gz files in /usr/share/fonts/terminus as well. This appears to work for me so far, but let's see what people report when the 4.48-2 package builds hit updates-testing in a few hours. If there is a problem with this many OTB files or any other aspect of the fontforge generated OTB files, we can still change to using fonttosfnt in 4.48-3 later. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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 03 Jan '20

03 Jan '20

https://bugzilla.redhat.com/show_bug.cgi?id=1748495 --- Comment #31 from Peng Wu <pwu(a)redhat.com> --- I think fonttosfnt upstream is reviewing the merge requests, and they may release the tar ball later. Could you combine the fonts with the same family name and style name into one OpenType font? I suspect several OpenType fonts with the same family name and style name may cause problem when selecting the fonts. Maybe we can keep the old fonts for backward compatibility. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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 03 Jan '20

03 Jan '20

https://bugzilla.redhat.com/show_bug.cgi?id=1748495 --- Comment #30 from Hans Ulrich Niedermann <rhbugs(a)n-dimensional.de> --- I have found two ways to generate *.otb files for Terminus so far. Those are: 1. the fonttosfnt way which generates * one TerminusBold.otb from ter-u*b.bdf and * one TerminusNormal.otb from ter-u*n.bdf with commands like fonttosfnt -b -c -g 2 -m 2 -o TerminusBold.otb ter-u*b.bdf fonttosfnt -b -c -g 2 -m 2 -o TerminusNormal.otb ter-u*n.bdf 2. the fontforge way which generates * one ter-*[bn].otb for every ter-*[bn].bdf with a number of commands like fontforge -lang=ff -c 'Open("ter-u12b.bdf"); Generate("ter-u12b.otb")' At this time, I am inclined towards the fontforge way, as this uses the stock fontforge shipped with Fedora, not from some COPR. Now I am trying to read the current font guidelines, to fish out the information applying for bitmap fonts from amongst instructions using tools not shipped in Fedora at all (ttname), applying to vector fonts only, etc. I still want to maintain backward compatibility with older software which still uses the old fonts through old rendering libraries. Not everyone is using Pango and Gnome, after all. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

fonts-bugs January 2020