Distinguish designed damage from a damaged font file
Patrick Griffin’s Broken account describes Egyptian-style forms inspired by the early and middle nineteenth century. The digital design simulates imperfect punches, ink spread and fragments associated with worn printing. These are intentional glyph details. The family name does not diagnose a corrupted font, and its appearance is not evidence that a particular historical document was printed with it.
Use the second capital set deliberately
Canada Type documents two interchangeable sets of uppercase letters. Set BROKEN RECORDS and compare the two Rs using the original family’s character controls. Keep one version unchanged while substituting a single alternate in the other. Then inspect the entire title at its final size. The exercise is to distribute the built-in irregularity, not to add another distress filter before seeing what the letters already contain.
Make the archive label usable as well as atmospheric
Place ARCHIVE 08 and the date in a plain companion so the distressed heading has a distinct job. Retain the exact title as ordinary text in the handoff, together with the font and alternate choices. Anton and Bitter are independent comparisons here. The homepage’s portable text generator changes Unicode characters; it does not reproduce Broken’s simulated print damage or repair a malfunctioning font file.
Your questions, answered.
Why do repeated capitals look different?
The publisher supplies two interchangeable uppercase sets. Select alternates intentionally rather than assuming the difference is a rendering error.
Is this a guide to fixing a broken font?
No. It covers Patrick Griffin’s named Canada Type design and its simulated print-wear details.
Sources & background
Sources supporting this page’s explanations. Practical examples are our editorial suggestions.