Using a Font-Specific Unicode–Name Mapping
A project can use its own .nam mapping when its glyph-name conventions differ from the standard table. The choice belongs to the font, so two open fonts can resolve names differently without replacing the application’s standard mapping.
Choose the Mapping File
- Save the font if you intend to use a path relative to its source file.
- Open Font Info > Other Values and locate Unicode–name mapping.
- Set Mapping file to a valid
.namfile. Use an absolute path or a path relative to the saved font. - Apply the Font Info changes with Apply or OK, and inspect the mapping status.
- Check a representative name-to-Unicode operation and the resulting glyph identities before using the mapping for a batch operation.
The setting supplies the font’s name-resolution table to operations such as naming, construction, and property searches. It does not itself request a wholesale rename or reassignment of existing glyphs. Keep the distinction between an existing Unicode assignment and a name-derived classification.
Reload or Return to Standard Mapping
After changing the external file, click Reload beside the mapping file to read it again. The new mapping is staged until Apply or OK; canceling Font Info keeps the previous mapping. Inspect Status for errors before accepting the result.
Clear Mapping file to use the standard mapping. An unreadable or invalid file reports its error and falls back to standard mapping. A relative path cannot be resolved for an unsaved font; save the font first or use an absolute path.
Keep the Mapping with the Project
Include the external .nam file in a project handoff and check the path after moving or saving the font elsewhere. A saved path is not a substitute for supplying the mapping file itself. Confirm the active mapping before comparing filtering or naming results between computers.