Skip to content

Save System

sequenceDiagram
    participant D as bited database
    participant B as bited
    participant F as bdf file<br>glyphs.toml
    participant V as version control<br>(e.g. git)

    activate B
    alt
        note over B: make changes to font
        B->>D: autosave
    else
        note over B: save to bdf (Ctrl+S)
        B->>F: save
        opt
            F->>V: push
        end
    else
        opt
            V->>F: pull
        end
        note over B: load from bdf (Ctrl+O)
        F-->>B: load
    end
    deactivate B

Database

After each change you make to your font, bited autosaves to saves.db, a SQLite database of all the fonts that you loaded into bited. bited also reads from saves.db when loading fonts from the start menu.

Location of saves.db
OS Path
Windows %APPDATA%\bited\saves.db
MacOS ~/Library/Application Support/bited/saves.db
Linux ~/.local/share/bited/saves.db

BDF File

Since BDFs are both human-readable and machine-renderable, saving to BDF (Ctrl+S) serves both as a backup and an export. BDFs are also very diff-friendly, so I highly recommend committing your BDF to a version control system like Git. bited even includes metadata to ensure that bited BDFs are reproducibly editable across different machines.

To reload a BDF back into bited -- e.g. after pulling from version control or externally making changes -- simply load from BDF (Ctrl+O).