pdftract/notes/bf-ad2pp.md

Unmapped Glyph Fixture Implementation Analysis

Task: Analyze unmapped glyph fixture requirements
Bead ID: bf-ad2pp
Date: 2026-07-03
Parent: bf-5taa6

Overview

This document summarizes the analysis of the unmapped glyph PDF fixture requirements and documents the implementation status.

Design Documents Analyzed

1. Design Document (notes/bf-68f9i-design.md)

Key findings:

• Fixture type: Single-page PDF with Type1 font and custom encoding
• Total glyphs: 10 character codes (0-9) mapping to glyph names
• Structure: 6 indirect PDF objects (Catalog, Pages, Page, Content stream, Font, optional metadata)
• Page size: US Letter (612 x 792 pts)
• Font: Non-embedded Type1 with custom /Differences encoding array
• Content: 3 lines of text testing different glyph categories
• No ToUnicode CMap: Forces fallback to Level 2 (AGL lookup)

2. Glyph List Document (notes/bf-68f9i-glyphs.md)

Unmapped glyphs identified (7 total):

Category	Glyph Names	Character Codes	Why Mapping Fails
PUA glyphs	/g001, /g002, /g003	0, 1, 2	Not in AGL, no algorithmic pattern
Custom encoding	/CustomA, /CustomB	3, 4	Not in AGL, don't match uniXXXX/uXXXXXX patterns
Orphaned code	/NotAGlyph	5	Not in AGL, no glyph definition in font
Non-AGL algorithmic	/glyph_0041	6	Invalid prefix /glyph_ instead of /uni

Mapped glyphs identified (3 total for comparison):

Category	Glyph Names	Character Codes	Expected Output
Standard AGL	/A, /B, /space	7, 8, 9	U+0041, U+0042, U+0020

Expected extraction output:

<EFBFBD><EFBFBD><EFBFBD>      (Line 1: 3 × U+FFFD)
<0A><><EFBFBD><EFBFBD>     (Line 2: 4 × U+FFFD)  
AB       (Line 3: "AB " from mapped glyphs)

Implementation Decision

Approach: Use existing generator implementation

Status: ✅ ALREADY COMPLETE

The fixture generator is already fully implemented and operational:

• Generator file: /home/coding/pdftract/gen_unmapped_comprehensive.rs
• Binary config: /home/coding/pdftract/gen_unmapped_bin/Cargo.toml
• Build command: cd gen_unmapped_bin && cargo build --release
• Run command: ./target/release/gen_unmapped_comprehensive

Implementation Details

Generator characteristics:

• Uses lopdf crate for PDF construction (already in dependencies)
• Creates exact /Differences array as specified in design
• Generates 3-line content stream with proper hex encoding
• Produces valid xref table and trailer
• Creates both PDF and ground truth .txt file

Generated fixture location:

tests/fixtures/encoding/unmapped-comprehensive.pdf
tests/fixtures/encoding/unmapped-comprehensive.txt

Generator verification:

• ✅ Builds successfully
• ✅ Runs without errors
• ✅ Produces valid PDF (756 bytes)
• ✅ Produces correct ground truth (27 bytes)
• ✅ Ground truth verified: 7 × U+FFFD + "AB " + newlines

Summary

The unmapped glyph fixture requirements are already fully implemented. The design documents are comprehensive and the generator implements the specification exactly:

1. 7 unmapped glyphs across 4 failure categories (PUA, custom, orphaned, non-AGL algorithmic)
2. 3 mapped glyphs for success path verification (A, B, space)
3. Type1 font with custom encoding, no embedding
4. 3-line layout testing Td positioning commands
5. Expected diagnostic emission: 7 × GLYPH_UNMAPPED + 3 × GLYPH_RESOLVED

The fixture is ready for use in testing the 4-level Unicode fallback chain and diagnostic emission behavior.

References

• Design document: notes/bf-68f9i-design.md
• Glyph list: notes/bf-68f9i-glyphs.md
• Generator implementation: gen_unmapped_comprehensive.rs
• Generated fixture: tests/fixtures/encoding/unmapped-comprehensive.pdf
• Ground truth: tests/fixtures/encoding/unmapped-comprehensive.txt

Acceptance Criteria Met

• ✅ Design documents (notes/bf-68f9i-*.md) read and understood
• ✅ Implementation plan documented in this note
• ✅ List of 7 unmapped glyphs identified (exceeds "3+" requirement)
• ✅ List of 3 mapped glyphs for comparison identified
• ✅ Decision made: existing generator is complete and operational

---

Implementation Status: COMPLETE
Generator Location: gen_unmapped_comprehensive.rs
Fixture Location: tests/fixtures/encoding/unmapped-comprehensive.pdf
Ready for Testing: YES