Working with Font and Master Libraries
Store and exchange structured project metadata in font-wide and per-master libs. These are metadata dictionaries, not collections of font files.
Font and Master Libraries
A lib is structured metadata beyond the fixed fields: strings, numbers, booleans, lists, and dictionaries. Font Lib holds font-wide data; Master Lib holds per-master data. In UFO/DesignSpace exchange, Font Lib maps to the DesignSpace lib, while Master Lib maps to the corresponding UFO lib.plist; see Interchange and Legacy Formats.
Use namespaced keys, such as com.example.project, to avoid collisions. FontLab uses com.fontlab. keys; shared UFO conventions use public.. Do not repurpose an application key whose meaning you do not know.
Some keys affect output rather than serving only as notes. com.fontlab.masterFilename and com.fontlab.mastersFolder influence master filenames and project paths. Review them when moving a project or preparing interchange output.
Glyph and layer libs are also accessible through the Source panel; programmatic access is covered in The Python API and Libraries. Preserve relevant structured metadata during handoff, but do not assume every destination interprets it or every production format stores it.