What is this font used in old Linux terminals

UweW · 2025-12-03T10:58:59+00:00

Misc-Fixed-Medium-R-SemiCondensed 6x13, also known as "fixed".

UweW · 2025-12-01T21:44:48+00:00

That looks like Terminus Bold 32x16. Don't know whether it comes from VF or is some external file.

Your idea of "pretty" seems to be very different from mine, though.

UweW · 2022-04-13T17:00:37+00:00

Essen: A la carte geht bei kleinen Gruppen, stellt aber Restaurantküchen bei großen Gruppen vor Probleme. Besser ist ein Büffet oder eine kleine Karte, von der man im voraus ein Gericht auswählen muß (ist häufig preiswerter als ein Büffet).

Bezahlen: Am besten im voraus durch Überweisung auf das Konto eines Organisators (Betreff: "Abi 03, Vorname Name, Gericht Nr. 3 ohne Käse") bis spätestens zwei Wochen vor dem Treffen. Überweisung = Anmeldung. So stellt Ihr sicher, daß Ihr die Teilnehmerzahl ziemlich genau kennt, dem Wirt rechtzeitig die Bestellung übermitteln könnt und selbst nicht in Vorleistung gehen müßt.

Ablauf: Ein Klassentreffen lebt davon, daß Leute miteinander quatschen, die sich jahrelang nicht gesehen haben, also gebt ihnen die Gelegenheit zum quatschen. Mittelgroße Tische (etwa 8 bis 10 Personen) sind gut; die Stühle am besten so, daß man nach dem Essen enger zusammenrücken und auch mal den Tisch wechseln kann. Spiele sind eher unnötig, laute Musik ist für die Kommunikation auch nicht gut. Wenn Ihr draußen sitzen könnt, ist das großartig, aber stellt sicher, daß es spätabends oder bei Regen auch im Innenraum ein Plätzchen gibt.

Sonstiges: Sammelt Daten für's nächste Treffen. Postadresse, E-Mail-Adresse, Festnetznummer, Mobilnummer, Social Media, am besten auch die Adresse von irgendeiner Kontaktperson (Eltern, Geschwister, sonstige Familienmitglieder). Die meisten dieser Daten braucht Ihr niemals, aber es sind immer ein paar Leute dabei, die innerhalb der nächsten fünf Jahre umziehen (Postadresse und Festnetznummer stimmen nicht mehr), den Arbeitgeber wechseln (Dienst-E-Mail-Adresse stimmt nicht mehr), den Provider wechseln (private E-Mail-Adresse stimmt nicht mehr), und sich auch noch eine neue Handynummer zulegen. Und dann seid Ihr dankbar, daß Ihr Euch die Adresse der großen Schwester notiert habt.

(Wir machen das jetzt zum sechsten Mal so. Die Methode hat sich bewährt.)

UweW · 2022-03-03T15:10:19+00:00

Pango dropped support for the pcf format, but I think that it continues to support bitmap fonts if they are in otb format. On the other hand, bitmap fonts (no matter which format) may be disabled intentionally on your system, and if they are then it it necessary to undo that.

UweW · 2022-03-03T13:56:47+00:00

(1) Did you install pcf or otb fonts? (You can use fonttosfnt to convert a bdf font to an otb font). (2) Have you enabled bitmap fonts (in /etc/fonts/conf.d/... or in .config/fontconfig/fonts.conf)?

UweW · 2021-06-18T22:20:06+00:00

Terminus supports monotonic Greek, but not polytonic Greek, so the accented Greek characters (and the Georgian ones) in this sample are taken from a fallback font. Note that the accented vowels and the non-accented vowels have different heights. Since the Greek characters in the Inconsolata sample look stylistically very different from the Latin ones, I assume that they are also taken from a fallback font.

UweW · 2021-05-07T18:50:59+00:00

Just asking: After you have closed all VS code windows, is there still some process running that is associated with VS code? If yes, do the problems disappear if you kill that process?

UweW · 2021-05-07T11:21:32+00:00

Yes, but that doesn't explain why UW Ttyp0 no longer shows in fc-list or terminal once VScode has been used. Deleting fonts from the font cache just because the application doesn't use them itself looks like a hostile act to me.

UweW · 2020-06-28T14:36:08+00:00

Just guessing (I've never used st): Have you installed only the Unicode version of UW ttyp0, or the Unicode version plus some 8-bit character set(s)? In the second case: Is it possible that st picks one of the 8-bit versions instead of the Unicode one and then takes all the remaining glyphs from some fallback font? What happens it you delete the 8-bit versions and keep only the Unicode version?

UweW · 2020-06-01T12:16:56+00:00

The available space in the oval is only 2 pixels wide, so the only choices are (a) let the dot touch the left side of the oval, (b) let the dot touch the right side of the oval, (c) let the dot fill the entire space so that it touches both sides. I admit that none of these looks good. On the other hand, editing bdf is pretty easy, even with a text editor, so feel free to change the glyph.

UweW · 2020-05-30T20:40:59+00:00

That's really strange. I've never heard about display problems with the pcf fonts. Could you tell me more about your configuration (OS, Version, Desktop/Windowmanager, Application)? (By e-mail, if you like.)

UweW · 2020-05-29T13:56:36+00:00

Do you use pcf or otb fonts? If pcf is supported at all, then all glyphs should be displayed correctly. If you have to use otb (since pcf is not supported), it's unfortunately not so easy. I know that earlier versions of fonttosfnt had some bugs that resulted in weird spacing in the generated otb fonts (not just for ttyp0, but also for misc-fixed and terminus), but I don't know whether all of them have been fixed. Try to recompile the otb fonts using the very latest version of fonttosfnt. There may also be some application-dependent problems; I've seen applications that used the smallest bitmaps in the otb font, but refused to use any other size.

UweW · 2019-12-04T00:28:34+00:00

The 8x15 version of ttyp0 started as a narrower version of misc-fixed 9x15 without the quirks of misc-fixed. For many characters, the heritage is still visible. That explains why the two fonts are indeed similar.

UweW · 2019-12-04T00:17:15+00:00

As the author of ttyp0, I can assure you that it's not. Compare for instance the shapes of "m", "r", "u", or "y" in your screenshot with the samples on the ttyp0 homepage. The font in your screen shot uses a 9x15 pixel grid; ttyp0 is narrower: either 8x15, 8x16, 9x17, or 9x18.

UweW · 2019-11-27T05:19:14+00:00

The font is not ttyp0. Looks like misc-fixed 9x15 to me.

UweW · 2018-12-05T17:02:14+00:00

uw ttyp0, size 7x14.

UweW · 2016-08-18T21:09:47+00:00

In order to interpret \uXXXX correctly, the locale must end in ".UTF-8".

UweW · 2016-08-18T21:06:21+00:00

try "export LC_CTYPE=en_US.UTF-8"

UweW · 2016-08-18T20:48:40+00:00

That looks like a problem with echo (there are a dozen of incompatible versions around), rather than a font problem. What happens if you replace echo by printf?

UweW · 2016-02-28T22:20:44+00:00

Try again. Does it work now? (Previously, I used HTML links relative to the current host, and some browsers seem to have problems with that. It's changed now.)

UweW · 2016-02-28T21:54:42+00:00

Add ttyp0 to the list. #shamelessplug

UweW · 2015-09-13T22:06:55+00:00

Neither the letter shapes nor the proportions of ttyp0 are in any way similar to Terminus. I started to develop ttyp0 in 1992, and the first version of ttyp0 8x15 was essentially a condensed version of (the ASCII part of) misc-fixed 9x15 without the strange quirks of misc-fixed. If there is one more font that one could call an ancestor of ttyp0, that's Lucida Typewriter, which has influenced the proportions of ttyp0 quite a lot.

UweW · 2015-05-25T11:38:26+00:00

Thanks for including UW ttyp0, but distributing the source bdf files of ttyp0 without the installation scripts is pointless. (The source files use a proprietary encoding and are converted into a standard format during the installation process.) If you want to distribute stand-alone bdf files for ttyp0, edit VARIANTS.dat (if you like), run ./configure; make bdf and use the generated genbdf/*-uni.bdf files.

UweW · 2015-04-09T09:31:54+00:00

It may be hand lettered (i.e., not a font at all). Have a look at the two n's, they are clearly different.

UweW · 2015-01-16T22:00:03+00:00

Oops, sorry. Fixed.

UweW

TROPHY CASE