71339ec8afb5bbcaac8922ef4538f1c9ac944e5a jnavarr5 Fri Jun 26 11:58:46 2026 -0700 Reword the intro to the add-a-font steps in the mirror manual, refs #37698 diff --git src/product/mirrorManual.txt src/product/mirrorManual.txt index c874181c5fa..434d0da9311 100644 --- src/product/mirrorManual.txt +++ src/product/mirrorManual.txt @@ -1612,31 +1612,33 @@ 7af41ff3536fadcdc27eb9e5cc1c32d3 n021024l.pfb db95b702b81c12df1f91d15c8a6c3191 n022003l.pfb e97c9af68414fabe157af711b7691df7 n022004l.pfb f13fb8e581426a1ffa5fc12b10ad0f34 n022023l.pfb f3cd9244150f086434b62d5c5bb559b0 n022024l.pfb 30aef717b7c68a6b6b7760b764fbd01c z003034l.pfb # Adding a new font to the Genome Browser display The fonts offered in the hgTracks "configure" page Font menu are defined in a table in the source code: the `freeTypeFonts[]` array in `src/hg/hgTracks/config.c` ([view on GitHub](https://raw.githubusercontent.com/ucscGenomeBrowser/kent/refs/heads/master/src/hg/hgTracks/config.c)). Adding a font is therefore a source code change, and you will need to rebuild the CGIs afterward (see the [Building the kent source tree](#building-the-kent-source-tree) -section below). There are two steps. +section below). + +Once you have a font file in hand, adding it takes just two steps: 1. Put the font file where the rendering engine can find it. At run time the file is looked up under the directory given by the `freeTypeDir` setting in hg.conf, which defaults to `../htdocs/urw-fonts`. That path is relative to the CGI working directory, so it resolves to the shared `htdocs/urw-fonts` directory even when you run from a per-user sandbox; you do not need a copy under your own htdocs. Both Type1 (`.pfb`) and TrueType (`.ttf`) font files are supported. 2. Add a row to the `freeTypeFonts[]` table in `src/hg/hgTracks/config.c`, giving the name to display and the font file name, for example: {"Lexend", "Lexend-Regular.ttf"}, {"Lexend-Bold", "Lexend-Bold.ttf"},