PFB

Generated by scripts/gen-format-pages.py from docs/data/format-metadata/, FILE_FORMATS.csv and docs/formats-master.csv. Do not edit by hand: change the source, then run the script.

PostScript Type 1 PFB Preview.

At a glance

How much Poka reads

B4 Summary. The container and metadata are read and summarised (counts, properties, structure), but the main content is not rendered.

Confidence: medium (the reviewer read the code). Basis: Reviewed 2026-10-26: read parsers/poka-pfb/src/main.rs (531 lines) and plugin.json. No unit tests or tests/samples.rs; the corpus has sample.pfb, read by no test. Covers .pfb and .pfb-font. The tree lists the segments (type and length) and reads the FontInfo entries from the clear-text header (names, weight, version, notice, metrics, bounding box, encoding kind); a raw PFA is accepted too. Judgement: B4: the font's structure and names are decoded, but its glyphs are not.

What Poka does not read

• The eexec segment is not decrypted, so charstrings (glyph outlines) and private metrics are not read
• The font is not drawn
• A custom encoding is named as such, not listed

Libraries

Libraries Poka uses or has assessed for this format, with the status, licence and language the registry records.

• pdfrum-type1 (candidate; MIT OR Apache-2.0; Rust; https://github.com/PoHsuanLai/pdfrum) — Crate in the pdfrum workspace; README says it parses PFA and PFB containers (Container::Pfb), eexec and charstrings. Repo itself is a PDF library; licence taken from docs.rs crate page.
• stet-fonts (candidate; Apache-2.0 OR MIT; Rust; https://github.com/AndyCappDev/stet) — Pure-Rust Type 1/CFF/TrueType parsers; the stet workspace handles .pfb (system_fonts.rs, PFB header stripping in stet-pdf-reader). Whether the stet-fonts parser alone accepts raw PFB was not confirmed.

Sources

• parsers/poka-pfb/src/main.rs
• parsers/poka-pfb/plugin.json