UPDATE-XFONTS-TRADITIONAL(8)
π update-xfonts-traditional π
okay bestie, so this is a section 8 manual page from the chiark utilities family, and no, it's not a command you run casually β it's one of those maintenance-girlie system admin tools. let's get into it π
β¨ NAME β¨
update-xfonts-traditional β generate traditional ASCII fixed-with fonts πΈ
(yes, that's the actual wording, "fixed-with", we don't fix it, we preserve it fr fr π )
π¦ SYNOPSIS π¦
update-xfonts-traditional --bdf-filter
update-xfonts-traditional --process-pcf in.pcf.gz out.pcf.gz
update-xfonts-traditional --process-fontdirs fontdir ...
update-xfonts-traditional --process-fonttrees fonttree ...
update-xfonts-traditional --update
hmm wait, the --update mode is listed in MODES but not in the SYNOPSIS, so don't come for me, I'm just the messenger π
π DESCRIPTION π
so basically update-xfonts-traditional generates versions of X11 PCF fonts that have been edited to restore compatibility with traditional versions of US-ASCII, and to restore some of the glyphs to a more traditional appearance. it's giving "nostalgia restoration project" and honestly? iconic π
π MODES π
--bdf-filterβ takes a BDF on standard input and tries to generate an edited BDF on standard output. in-and-out, no drama β¨--process-pcfβ takes two PCF filename arguments (yes, that's a typo in the original, "Takes to PCF filename arguments", but you know what it means, bestie π«Ά). the input PCF gets uncompressed, decompiled to a BDF, processed, recompiled to a PCF and recompressed. it's the full glow-up pipeline π--process-fontdirsβ in each fontdir, all files namedfont.pcf.gzare processed, to generate where applicable correspondingtrad--font.pcf.gzfiles. and here's the smart part: the mtime, ctime and inode number of the input files are recorded, so that reprocessing the same directory later will be fast. efficiency queen behavior β‘--process-fonttreesβ each fonttree is searched for font directories, which are then processed as above. it goes hunting π--updateβ each built in font tree location is searched for font directories which are processed as above. the vibes are automatic π
π OPTIONS π
-R|--rules-pathrulespath β prepend rulespath to the path of directories from which to load glyph editing rules. yes, it's-R|--rules-path, pipe and all, that's literally how it's written π--share-dirshare-dir β use share-dir instead of/usr[/local]/share/xfonts-traditional. pick your own home, main character energy π--parallel|-jcpus β use up to cpus cores for processing fonts. the default is all the cpus available. we do not do half measures here π₯--always-reprocessβ when scanning font directories, always reprocess all the fonts, regardless of whether we think they have been done already. no skipping, no shortcuts, we do the work again πͺ--no-tolerate-bad-fontsβ treat bad input fonts (eg, ones for whichpcf2bdfcrashes, or ones with other problems) as a fatal error. normally they just produce a warning. so like, this is the strict mode, be careful bestie π
π FILES π
xfonts-traditional.doneβ in each font directory, records information about processed fonts, so as to optimise away unnecessary reprocessing. it's the receipts file π§Ύxfonts-traditional.logβ in each font directory, records a lot of which fonts were processed and to a certain extent if not why not. it's the diary π/usr/share/fonts/X11/usr/local/share/fonts/X11β default font tree paths for--update. those are the hangout spots πtrad--font.pcf.gzβ in any font directory, our output files. β οΈ any other files matching this pattern may be overwritten or deleted. so like, don't go naming your random files that, okay? π³
β EXIT STATUS β
0β all went well and there were no warnings. we love a clean run π₯³2β with--bdf-filterand--process-pcfonly, indicates that the input font did not need to be edited, or was not suitable for editing, and has not been written out, so the output is incomplete, but this is not an error. so don't panic, it's a soft no π- any other β there were problems. yeah. π
π BUGS π
only the 6x13 font is conventionally called supported. (that's exactly how it's phrased, "conventionally called supported", we keep it fr fr π)
and β and this is the sad part β this package comes too late to rescue Unix from an incompatible change to its character set. we tried, bestie. we really did. ππ«Ά
π that's a wrap π
sign-off time: this page is from Greenend, dated 2012, and it lives in section 8 of the manual β UPDATE-XFONTS-TRADITIONAL(8), chiark utilities edition. slay, stay traditional, and don't forget to back up before you let it delete anything matching trad--font.pcf.gz πβ¨ππ¦πΈπ
π«Ά
π¦ where this page comes from
- debian bookworm: xfonts-traditional 1.8.0+nmu1
- debian trixie: xfonts-traditional 1.8.2
- ubuntu jammy: xfonts-traditional 1.8.0+nmu1
- ubuntu noble: xfonts-traditional 1.8.0+nmu1
- ubuntu questing: xfonts-traditional 1.8.2
- ubuntu resolute: xfonts-traditional 1.8.2build1
- ubuntu stonking: xfonts-traditional 1.8.3
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms