Checking Font Metadata Naming Errors in FontForge

This guide explains how to use FontForge's built-in validation and diagnostic tools to identify and resolve font naming conflicts, metadata discrepancies, and OpenType specification violations. By utilizing the automated FontForge validation tool alongside font information panels, you can ensure your font files conform to cross-platform operating system standards and avoid rendering or installation errors.

1. Open the Font Information Panel

Before running automated validation, verify that your base naming tables are synchronized:

  1. Open your font project in FontForge.
  2. Navigate to Element > Font Info (or press Ctrl+Shift+F / Cmd+Shift+F).
  3. Check the PS Names tab to confirm the following fields:
    • Fontname: Must be a single PostScript name without spaces, typically under 31 characters, using only ASCII characters.
    • Family Name: The human-readable name of the font family.
    • Weight: Standard weights such as Regular, Bold, or Italic.
  4. Navigate to the TTF Names tab to ensure that the generated Windows and Macintosh platform strings match the PostScript specifications. Inconsistencies here are the most frequent source of metadata validation warnings.

2. Run the FontForge Validation Tool

FontForge includes an automated validator that audits both glyph outlines and font metadata against standard specifications:

  1. Go to the top menu and select Element > Validation > Validate.
  2. A progress bar will appear while FontForge inspects the entire font file.
  3. Once the process completes, the Validation Errors dialog box will appear.
  4. Review the top section of the window, which highlights font-wide and metadata issues. Common metadata errors flagged here include:
    • Non-ASCII characters in PostScript strings.
    • Duplicate or missing platform-specific name records in the name table.
    • Missing required TrueType/OpenType tables (such as OS/2 or head).
    • Invalid font vendor IDs or invalid license URLs.

3. Diagnose Issues Using the "Find Problems" Tool

To scan for specific naming and glyph-level metadata issues:

  1. Select all glyphs in your font (Ctrl+A or Cmd+A).
  2. Go to Element > Find Problems.
  3. Click on the Components and Misc tabs.
  4. Check the options for checking non-standard glyph names or duplicate unicode code points.
  5. Click OK to run the scan. FontForge will flag glyphs where metadata names deviate from the Adobe Glyph Naming (AGN) standard.

4. Resolve Common Metadata Errors

When FontForge reports metadata issues, apply the following fixes within Element > Font Info:

  • PostScript Name Exceeds Length Limit: Truncate the Fontname field to 31 characters or fewer and remove any spaces or special punctuation.
  • Mismatched Subfamily Strings: In the TTF Names section, select Styles and ensure the Typographic Family/Subfamily (Name IDs 16 and 17) align logically with the standard Family/Style (Name IDs 1 and 2).
  • Missing OS/2 Metrics or Panose Information: Open the OS/2 tab, verify the Weight, Width, and Vendor ID, and ensure that Panose digits are assigned or set to legitimate fallback values.

5. Validate Metadata During Font Generation

FontForge runs a final sanity check upon export:

  1. Navigate to File > Generate Fonts.
  2. Select your desired output format (such as OpenType CFF or TrueType).
  3. Click Generate.
  4. If unresolved metadata errors exist, FontForge displays a prompt listing remaining issues. Review this warning dialog carefully to ensure no critical name or OS/2 table warnings remain before finalizing the font.