https://bugzilla.redhat.com/show_bug.cgi?id=1753295
spamulousbastard+redhat(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |spamulousbastard+redhat@gma
| |il.com
--- Comment #83 from spamulousbastard+redhat(a)gmail.com ---
Having had some success with Terminus, I tried to convert TamzenForPowerline
(
https://github.com/sunaku/tamzen-font) to otb, with the method described in
Bug 1748495 comment 24. Even using the patched fonttosfnt from pwu's copr
(
https://copr.fedorainfracloud.org/coprs/pwu/fonttosfnt/), the result fails to
be detected as a monospace font, so cannot be selected in gvim or terminal
emulators, although it works fine in gedit.
I was able to get it to work, eventually, by opening all the .bdfs at once with
fontforge (fontforge TamzenForPowerline*.bdf; this opens over 9000 fontforge
windows), manually setting the width for each bitmap strike through the GUI
(encoding -> compact, drag select all, right click, set width, accept
suggestion), and then generating a TTC.
The manual width-setting step is necessary because otherwise the produced font
has zero spacing between characters. According to the discussion on this
fontforge bug:
https://github.com/fontforge/fontforge/issues/3853, the cause is
that fontforge itself relies on pango to load .bdf fonts. I.e., the conversion
of fonts to make them compatible with pango 1.44 does not work properly under
pango 1.44.
It is clear that inflicting this level of breakage in a minor version was a
gross error. The time to make this compatibility break, if it could be made,
was in 2006, when the automatic conversion program was fresh and maintained,
and the reliance on support for bitmap fonts was less. 13 years later, the
only option is to get off the pot.
I have taken the liberty of cursing the pango developers to only be able to use
< 100 physical PPI screens forevermore, and if you feel the same I encourage
you to donate your voodoo energies to reinforce it.
--
You are receiving this mail because:
You are on the CC list for the bug.