FONTTOSFNT(1)
π
FONTTOSFNT(1) β the fonttosfnt glow-up, bestie edition
okay so picture this: you've got a crusty little bitmap font, right? and you want it to live inside a shiny sfnt (OpenType) wrapper like it's moving into a cute new apartment. that's literally the whole job of fonttosfnt, and honestly? it ate. this page is from the General Commands Manual, section 1, and it's about to be your new hyperfixation. π
β¨ SYNOPSIS β¨
fonttosfnt [ options ] -o file.otb [ -- ] [ font ] ...
that's it. that's the whole summoning ritual. π«Ά
πΈ DESCRIPTION πΈ
so what it does: it wraps a bitmap font β or a whole set of bitmap fonts, yes you can bring your friends β inside a sfnt wrapper (that's TrueType or OpenType, for the uninitiated π ).
and if you don't name any font at all? no drama. it just reads a BDF font from standard input (stdin). slay, honestly. β¨
π₯ OPTIONS π₯
-vβ be verbose. it will yap. sometimes you want it to yap. π£οΈ-cβ do not crop glyphs. heads up: this usually makes the file bigger, but ngl, sometimes it actually yields a modest decrease in file size for small character cell fonts (you know, terminal fonts π).-bβ write byte-aligned glyph data. by default it writes unaligned data, which gives you a smaller file size. trade-offs, bestie π-rβ do not reencode fonts. by default, fonts get reencoded to Unicode whenever possible β which is iconic and usually what you want, but hey, sometimes you don't. π-g_n_ β set the type of scalable glyphs that we write. okay this one has lore:- if n is
0, no scalable glyphs are written β this is legal but lowkey confuses most current software π - if n is
1, a single scalable glyph (the undefined glyph) is written β this is recommended, but it triggers a bug in current versions of FreeType π - if n is
2(the default), a sufficiently high number of blank glyphs are written, which works with FreeType but increases file size π«
- if n is
-m_n_ β set the type of scalable metrics that we write:- if n is
0, no scalable metrics are written, which may or may not be legal π - if n is
1, full metrics for a single glyph are written, and only left sidebearing values are written for the other glyphs - if n is
2, scalable metrics for all glyphs are written, which increases file size and is not recommended π - the default is
1π§
- if n is
--β end of options. nothing to see here, we're done with flags, move along β¨
π BUGS π
some of the font-level values β notably sub- and superscript positions β are dummy values. like, placeholder numbers. not the real thing. don't @ me, it's just how it is π
π SEE ALSO π
β¦and, for the vibes: Fonts in X11. π
π AUTHOR π
the version of Fonttosfnt included in this X.Org Foundation release was originally written by Juliusz Chroboczek <jch@freedesktop.org> for the XFree86 project. absolute legend behavior, tbh. periodt. π«Ά
ngl bestie, if you're wrapping terminal fonts, maybe give-ca try and see if it actually shrinks things for you β the manpage says it might. no cap, just read the-cbullet again. π
okay that's the whole page, mwah π β this was fonttosfnt 1.2.4, X Version 11, and you're officially caught up. go wrap some fonts. π¦
π¦ where this page comes from
- fedora 43: fonttosfnt 1.2.4-3.fc43 Β· MIT
- fedora 44: fonttosfnt 1.2.4-4.fc44 Β· MIT
- opensuse-leap 16.0: fonttosfnt 1.2.4-160000.2.2 Β· MIT
- opensuse-leap 16.0: fonttosfnt 1.2.4-160000.2.2 Β· MIT
- opensuse-leap 16.0: fonttosfnt 1.2.4-160000.2.2 Β· MIT
- opensuse-leap 16.0: fonttosfnt 1.2.4-160000.2.2 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms