Typographic punctuation: refine the marks that shape reading
Check quotation marks, apostrophes, dashes, ellipses, and spacing as part of a consistent editorial system, while preserving code, measurements, and language-specific conventions.
Separate meaning from appearance
Punctuation belongs to the language and editorial system as well as the visual design. Begin by preserving the intended meaning and the conventions of the document's language. A typographic refinement should not silently change a technical expression, a quoted passage, or a measurement into something different.
Collect the punctuation patterns the project actually uses: quotations, contractions, ranges, interruptions, abbreviations, and perhaps code or mathematical notation. Set them in the chosen font. Missing or awkward marks can become obvious only when the real text appears, especially when several styles or languages share one document.
Inspect quotes and apostrophes
Curved quotation marks and apostrophes often suit finished prose, but automatic replacement needs checking. A leading apostrophe in an abbreviated year or a word with an unusual prefix may be turned the wrong way. Inspect the actual characters rather than assuming the application's smart punctuation setting is always correct.
Keep literal technical contexts intact. Straight marks can have a functional role in code and other exact text. Do not apply a global visual cleanup without considering those sections. A document may reasonably use refined prose punctuation and literal code punctuation side by side because the content roles differ.
Use dashes and dots consistently
Hyphens, en dashes, and em dashes have different conventional uses, though editorial practices vary. Choose a style appropriate to the language and publication, then apply it consistently. A range, a compound word, and an interruption should not be converted indiscriminately to the same mark merely because it looks longer.
Check ellipses and surrounding spaces as part of that style. A built-in ellipsis character and three periods can behave differently in spacing and line breaking. The practical question is whether the result is clear, consistent, and appropriate to the content. Avoid inventing a universal rule where the publication's chosen style should guide the decision.
Proof in context
Read the final text for meaning, then inspect display lines for spacing around punctuation. A large opening quote or terminal mark can affect the apparent alignment of a headline. Adjust display treatment carefully while keeping the actual text intact and readable.
Use search to locate inconsistent patterns, but review each replacement when the context may differ. Automated cleanup is valuable for a long document, yet it can spread an error quickly. Keep a brief editorial note describing the chosen conventions so future contributors can match them without guessing from a handful of examples.
Try it yourself
- Identify language, editorial conventions, and literal technical contexts.
- Check automatic replacements and punctuation in the actual font.
- Use targeted searches with contextual review and a short style note.
Exercise: a punctuation specimen
Create a fictional exhibition notice containing a quoted title, a date range, a contraction, a parenthetical interruption, an ellipsis, and a short code example. Set the prose in the publication's chosen punctuation style while leaving the code literal. Inspect every automatic apostrophe and quote replacement. Then enlarge the title and examine how its opening quotation mark affects apparent alignment. Keep a copy of the specimen as a proofreading reference, with a note explaining the style decisions rather than presenting them as rules for every language.
References & further reading
Examples and exercises in this guide are original teaching scenarios.
