Package Details: terminus-font-ttf 4.49.3-1

Git Clone URL: (read-only, click to copy)
Package Base: terminus-font-ttf
Description: Monospaced bitmap font designed for long work with computers (TTF version, mainly for Java applications)
Upstream URL:
Licenses: custom:OFL
Submitter: Tblue
Maintainer: Tblue
Last Packager: Tblue
Votes: 191
Popularity: 0.81
First Submitted: 2010-04-11 13:30 (UTC)
Last Updated: 2023-04-28 18:27 (UTC)

Pinned Comments

Tblue commented on 2010-04-11 13:34 (UTC) (edited on 2016-05-04 21:35 (UTC) by Tblue)

Please note that these fonts are not perfect (the outlines are not very good); use the font files provided by the terminus-font package instead when possible, their quality should be much better. These TTF files are mainly intended for use by Java applications which do not support fontconfig, like Netbeans -- the subpar outlines are not a problem in those applications because Java uses the (good) bitmaps anyway.

Latest Comments

1 2 3 Next › Last »

Tblue commented on 2023-04-28 00:04 (UTC)

VorpalGun, sorry for overlooking your comment!

Seems like Fontconfig does realize that this is a monospaced font:

% fc-query -f '%{spacing=}\n' /usr/share/fonts/TTF/TerminusTTF.ttf

A spacing of 100 means mono according to fonts-conf(5).

I think the issue is not with the font, but with your Fontconfig pattern. If we ask Fontconfig to prefer monospaced fonts, the sorted font list also includes only monospaced fonts:

% fc-match -sf '%{=fcmatch} %{spacing=}\n' 'Terminus (TTF):mono' | head -5
TerminusTTF.ttf: "Terminus (TTF)" "Medium" spacing=100
DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book" spacing=100
DejaVuSansMono-Bold.ttf: "DejaVu Sans Mono" "Bold" spacing=100
DejaVuSansMono-Oblique.ttf: "DejaVu Sans Mono" "Oblique" spacing=100
l047013t.pfa: "Luxi Mono" "Regular" spacing=100

Compare with the pattern Terminus (TTF), which tells Fontconfig the family name, but nothing about the preferred spacing:

% fc-match -sf '%{=fcmatch} %{spacing=}\n' 'Terminus (TTF)' | head -5
TerminusTTF.ttf: "Terminus (TTF)" "Medium" spacing=100
DejaVuSans.ttf: "DejaVu Sans" "Book" 
DejaVuSans-Bold.ttf: "DejaVu Sans" "Bold" 
DejaVuSans-Oblique.ttf: "DejaVu Sans" "Oblique" 
DejaVuSans-BoldOblique.ttf: "DejaVu Sans" "Bold Oblique"

I.e. try pattern Terminus (TTF):mono instead of just Terminus (TTF).

VorpalWay commented on 2022-06-10 18:30 (UTC)

Hi! It seems fontconfig does not understand that this is a monospace font, and thus uses sans-serif as a fallback font for missing glyphs. I believe a config file like the following needs to be installed:

    <family>Terminus (TTF)</family>

The following command can be used to list fallback order (after updating the cache with fc-cache):

fc-match -s 'Terminus (TTF)'

m040601 commented on 2020-11-09 01:28 (UTC) (edited on 2020-11-09 01:34 (UTC) by m040601)

Is this package wrongly flagged out of date ?

freed00m flagged terminus-font-ttf out-of-date on 2020-07-13 for the following reason:
Version 4.48

However neither, exists anymore, neither this PKGBUILD builds from there.

This PKGBUILD builds from,, which has its author says,

I post release announcements on my blog
that should make it easier to keep up with new releases.

Its author is in fact the same person who maintains this package, Tblue. One can confirm that the latest release is in fact still 04.47,

So that URL is wrong, and this package should not be marked "out of date"

Tblue commented on 2016-05-08 18:02 (UTC)

FYI, this TTF version now again is a direct conversion of Terminus Font (without any changed/added glyphs and without any upstream patches).

hexchain commented on 2015-07-31 16:59 (UTC)

This generated TTF still has Visual Studio fix?

dumbocove commented on 2015-01-16 01:15 (UTC)

Thank you. Tblue. Start knowing little about PKGBUILD. Hope I can also contribute something to the community!

Tblue commented on 2015-01-15 17:46 (UTC)

The trailing 3 in 4.39-3 is the package release number, not the version number of the packaged TTFs. :-) The fonts itself are still at version 4.39 and there hasn't been a new release for a while. - Package release 3 uses "fc-cache -s" instead of "fc-cache -sf" after installation and updating, which should speed up font cache generation since it does not force regeneration of all font caches, but only regenerates those which are out of date. - Package release 2 added a package() function to the PKGBUILD. That function used to be optional, but the latest makepkg release requires it to be present. If you are interested in the details, please look here:

dumbocove commented on 2015-01-14 22:34 (UTC)

Just curious what's the update in this 4.39-3 ? While official versions are all staying with 4.39. Thanks.

Tblue commented on 2014-06-15 12:58 (UTC)

Thanks, fixed.

bidulock commented on 2014-06-14 03:36 (UTC)

using a PKGBUILD without a package() function is deprecated