This repository documents how to build a Nerd Fonts-patched version of MonoLisa Code from locally supplied MonoLisa font files.
MonoLisa is a commercial font. Keep the original files in input/ and do not
redistribute generated fonts unless your MonoLisa license allows it.
Place the MonoLisa Code .ttf files in input/.
The easiest reproducible route is the official Nerd Fonts patcher Docker image. It wraps FontForge and the Nerd Fonts glyph sources. The wrapper pins the default image by digest so repeated builds use the same patcher unless you override it.
./scripts/patch.shTo see the wrapper inputs, outputs, environment variables, and docs:
./scripts/patch.sh --helpTo check local prerequisites without running the patcher:
./scripts/doctor.shGenerated fonts are written to output/, which is also ignored by git.
The wrapper keeps successful builds quiet and writes the full upstream patcher
log to output/patch.log.
Set PATCH_CLEAN=1 to remove old generated .ttf and .otf files from
output/ before rebuilding:
PATCH_CLEAN=1 ./scripts/patch.shTo pass extra options to the Nerd Fonts patcher, append them:
./scripts/patch.sh --debugSet PATCH_VERBOSE=1 when you want to see the raw FontForge and patcher output:
PATCH_VERBOSE=1 ./scripts/patch.shSet NERD_FONTS_PATCHER_IMAGE to use a different patcher image:
NERD_FONTS_PATCHER_IMAGE=nerdfonts/patcher:latest ./scripts/patch.shThe script patches temporary copies of the input fonts. This keeps the
commercial source files in input/ untouched while still allowing FontForge to
perform its metadata checks and fixes.
- Patcher options: default flags, common upstream flags, and pass-through examples.
- Maintenance: troubleshooting, manual Docker usage, and patcher image update checks.
- Vercel web UI plan: hosted UI architecture and rollout plan.