Exporting
Export builds a font file. A project build script wins; otherwise it compiles with fontc.
| Status | Implemented, native only |
|---|---|
| Stability | Stable |
Export
Press Cmd+E, or use File → Export. Unsaved masters are
saved first, so what you export is what is on disk.
A Build Script Wins
Runebender looks for build-fontc.sh or build.sh beside your
source, then in each parent directory, stopping at the repository
root. If it finds one, it runs that script and reports where the
output landed.
This is deliberate. A project that already builds a specific way should keep building that way, and the editor should not be a second opinion about how your font is made. Google Fonts projects usually have such a script already.
The script runs with a repaired PATH, so a project .venv, cargo
binaries, and Homebrew are all reachable even when the application was
launched from the Dock.
Otherwise fontc
With no build script, Runebender compiles the source with fontc and writes the result next to it.
Install fontc if you do not have it.
cargo install fontc Runebender looks for fontc on your PATH, then in
~/.cargo/bin. If neither has it, export stops and says so.
Production Names
Names in public.postscriptNames are applied on export, so working
names in your source do not have to be the names that ship.
Single Glyphs
Glyph → Export Glyph as SVG writes the current glyph as an SVG file beside the source. It is for a drawing you want outside the font, not part of the font build.
Export and SVG export are native only. The browser build cannot write to your disk.