Skip to content

Main content

Glyph ID Coverage Audit

Audit observed glyph metric IDs against an explicit font inventory, preserving occurrence indexes and missing metrics; no font-file lookup or fallback shaping.

Loading tool…

Description

Audit observed glyph metric IDs against an explicit font inventory, preserving occurrence indexes and missing metrics; no font-file lookup or fallback shaping.

A glyph’s advance moves the next placement origin; its ink box describes visible bounds relative to that origin. Ink can overhang the advance, and an unknown box differs from a known empty box. These tools use caller-supplied glyph IDs and metrics, placing a horizontal run by cumulative advances without shaping text.

Audit observed glyph metric IDs against an explicit font inventory, preserving occurrence indexes and missing metrics; no font-file lookup or fallback shaping.

When to use this tool

Use this tool to audit observed glyph metric IDs against an explicit font inventory, preserving occurrence indexes and missing metrics; no font-file lookup or fallback shaping.

How to use the tool and how it works

  1. Enter glyphsJson, available using the input definitions below. Serialize the JSON text fields in the decoded shape shown below.
  2. Run the operation. Resolve malformed-input errors before interpreting the result.
  3. Read result.missing. Interpret signs, units, ordering and null values using the rules below.

Compare each observed glyph ID exactly against the supplied available-ID list. Return every missing occurrence as {index,id}, preserving repeated observations.1

Input fieldMeaning and unitsAccepted input
glyphsJsonJSON array of {id, advance, cluster, box} glyph records. id is a string; advance is finite and may be signed; cluster is an integer 0–8192; box is null or [minX,minY,maxX,maxY] with ordered finite bounds.Text, at most 8,192 UTF-16 code units; the stated grammar and narrower limits also apply.
availableCaller-supplied available glyph-ID strings.Dense list of at most 128 strings, each at most 8,192 UTF-16 code units.

These decoded examples show the structure of the JSON text fields. Supply each as its corresponding serialized JSON string.

json
{
  "glyphsJson": [
    {
      "id": "a",
      "advance": 4,
      "cluster": 0,
      "box": [
        0,
        -1,
        3,
        2
      ]
    },
    {
      "id": "b",
      "advance": 5,
      "cluster": 1,
      "box": null
    }
  ]
}
Output fieldInterpretation
resultObject containing the fields below.
result.missingOriginal {index,id} observations absent from the supplied inventory.
json
{
  "input": {
    "glyphsJson": "[{\"id\": \"a\", \"advance\": 4, \"cluster\": 0, \"box\": [0, -1, 3, 2]}, {\"id\": \"b\", \"advance\": 5, \"cluster\": 1, \"box\": null}]",
    "available": [
      "a"
    ]
  },
  "output": {
    "result": {
      "missing": [
        {
          "index": 1,
          "id": "b"
        }
      ]
    }
  }
}

Limitations and assumptions

  • The inventory is supplied by the caller and is not checked against a font file or fallback shaping process.
  • All advances, box coordinates, shifts and positional tolerances must share caller-defined metric units. Signed advances are accepted. Glyph records contain id, advance, integer cluster 0–8192 and box = null or [minX,minY,maxX,maxY] with ordered bounds.
  • Every declared top-level input is required and unknown fields are rejected. Ordinary strings are limited to 8,192 UTF-16 code units and lists to 128 entries, with tighter operation-specific bounds where stated. JSON text has bounded nesting and node counts.
  • Numeric outputs must be finite and within the absolute safe-integer magnitude; exact larger integers use decimal text. Source positions are zero-based UTF-16 offsets and span ends are exclusive unless a different convention is explicitly stated.

Alternative or Complementary methods

Obtain metrics and cluster mappings from the intended font/shaping system, then inspect the supplied observations. Use actual rendering when hinting, fallback choice or visible pixel extents matter.

References

  1. Tool behavior and example: Glyph ID Coverage Audit — tool.io

Similar or alternative tools

  • Glyph Advance Run Tab Stop Placement

    Place glyph-run tab positions at the next strictly greater explicit stop, then repeat a supplied positive interval after the last stop; no text shaping.

  • Glyph Advance Scale Transform

    Scale explicit glyph advances and known box coordinates by a nonnegative uniform factor; no hinted rasterization or font metric inference.