Skip to main content

max / alloy

Audit Departure Mono's coverage, and record that it is not in the image Answers the coverage question the open-questions bundle carried, and turns up something more useful than the answer. Measured: 11,468 glyphs, 169 declared languages. Latin, Cyrillic, Greek, box drawing, and the Nerd Font private-use icons. No CJK, Arabic, Hebrew, Devanagari, Thai, Bengali or Tamil, and no Vietnamese. Vietnamese is the one worth naming: it is Latin-script and looks like it should work, so stacked diacritics fall back mid-word rather than failing visibly. The structural finding is that Departure is not installed at all. The font layer takes IosevkaTerm Nerd and Atkinson Hyperlegible and nothing else, and the only copy in the repo is a mockup asset under docs/mockups/fonts. So anything naming the family at runtime gets a silent fontconfig substitution, the same defect class as the emoji alias that named a font the image never installed. Drops "the console and alloy_tui" from the list of surfaces it is reserved for. A TUI cannot select a font: every cell is drawn in whatever the terminal is configured with, and the build already asserts that is IosevkaTerm. The surfaces where Departure can actually apply are the ones rendered outside the running system.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-08-05 16:50 UTC
Signed with PGP, not checked
Commit: c78ac71260a4261c6fd45c3cc2504dd228095ba4
Parent: 0dbf1f2
1 file changed, +5 insertions, -1 deletion
M docs/STACK.md +5 -1
@@ -503,7 +503,11 @@
503 503
504 504 Optimized for readability. A single fontconfig at `~/.config/fontconfig/fonts.conf` routes every app that asks for a generic family to Alloy's picks. Config at [`etc/skel/.config/fontconfig/`](../etc/skel/.config/fontconfig/).
505 505
506 - **Departure Mono, Alloy's brand mark, is not in the fontconfig chain.** It stays reserved for authored surfaces (the console and `alloy_tui`, headers, brand elements) and is invoked by name where wanted. Nobody reads code or long text in Departure.
506 + **Departure Mono, Alloy's brand mark, is not in the fontconfig chain.** It stays reserved for headers and brand elements and is invoked by name where wanted. Nobody reads code or long text in Departure.
507 +
508 + **It is also not in the image, which is the more useful fact.** Audited 2026-08-05. The font layer installs IosevkaTerm Nerd and Atkinson Hyperlegible and nothing else, and the only copy in the repo is `docs/mockups/fonts/DepartureMonoNerdFontMono-Regular.otf`, a design-time asset. So Departure is a font for things rendered *outside* the running system: mockups, the README and social card, a swaylock background plate, a first-boot splash image. Anything that names the family at runtime gets a silent fontconfig substitution, which is the same defect class as the emoji alias that named a font the image never installed. Naming it in a theme is therefore not a way to get it.
509 +
510 + **Measured coverage, for whoever reaches for it in a mockup:** 11,468 glyphs across 169 declared languages. Latin, Cyrillic and Greek, the box-drawing range, and the Nerd Font private-use icons. It does not cover CJK, Arabic, Hebrew, Devanagari, Thai, Bengali or Tamil, and it does not cover Vietnamese, which is the one worth knowing: Vietnamese is Latin-script and looks like it should work, so a string with stacked diacritics falls back mid-word rather than failing visibly. For a brand mark set in English that is an acceptable limit rather than a gap, and it is the reason the font stays out of the generic-family chain where a page of arbitrary text would hit it.
507 511
508 512 ### Monospace: **IosevkaTerm Nerd Font Mono**
509 513