A little help goes a long way. Find a tool/

Text FIELD NOTES · 4 MIN READ

Straight Quotes, Curly Quotes, and the Dashes Between

Why ASCII gave every key one job — and how typographic quotes, en and em dashes, and a real ellipsis differ from the plain versions.

The document looked perfect until someone printed it. Suddenly the quotes leaned the wrong way, the dashes were all the same length, and "wait..." wore three periods where one wide character should be. None of this is a mistake in your writing — it is ASCII showing through. Typewriters and early terminals gave every key exactly one job, and forty years later our drafts still ship with those compromises unless we convert them deliberately.

ASCII gave every key exactly one job

When the American Standard Code for Information Interchange was drawn up in 1963, it had to fit 128 characters into 7 bits, and the physical keyboards it described had single keys where typography wanted several. One double-quote character (") served as both an opening and a closing quote. One apostrophe (') did double duty as a quote mark and an elision marker. One hyphen (-) had to stand in for three different dashes. Three full stops (...) simulated a pause that professional typesetting had rendered with a single glyph for a century. These substitutions were invisible on paper printouts and perfectly acceptable in telegrams. They are far less acceptable in a 2026 newsletter.

Quotes have an open and a close

Proper typography uses four curved quote characters: opening “ and closing ” for double quotes, opening ‘ and closing ’ for single quotes. The shapes are not decoration — they curl toward the text they enclose, which is how readers parse quotations at a glance. The closing single quote has a second job: it is also the apostrophe. In “don’t”, the character before s is typographically a closing quote, because the mark stands where a letter was removed. This is why any smart-quote conversion has to make a positional decision: a quote that follows whitespace or an opening bracket usually opens a quotation, while one that follows a letter closes it or marks a contraction. The heuristic is not perfect — nested quotes can fool it — but it resolves ordinary prose correctly, which is why every word processor ships the same trick.

Three dashes, three jobs

The hyphen, en dash and em dash form a length ladder, and each rung has its own meaning. The hyphen (-) joins: well-known, twenty-three, phone numbers. The en dash (–, the width of an n) spans ranges like 10–20 and, in the spaced style common in British and web writing, marks asides: “open the menu – it is right there”. The em dash (—, the width of an m) is the dramatic one: it interrupts the sentence — sometimes twice — with real force. The keyboard offers only the first of these, which is why rough drafts grow double hyphens: “--” is a typist’s mnemonic for the em dash that the tools of the 1970s could not display. Converting “--” to “—”, and a spaced lone hyphen to an en dash, is the single highest-value pass you can run on a draft.

The ellipsis is one character

Three periods “...” set differently from the true ellipsis character “…”: the dots are wider, the spacing is even, and — crucially for layout — the whole thing is one unbreakable unit. A sentence can wrap between the three periods of a typed ellipsis and strand two dots at the end of a line; the glyph cannot be split. The ellipsis character also survives search-and-replace, screen readers and string comparison in a way that “dot dot dot” never reliably does.

When not to normalize

Conversion is for prose, not for everything. Curly quotes are not string delimiters in most programming languages, so running a normalizer over source code breaks it. A curly quote pasted into a URL is a different byte sequence that will not resolve. Mathematics and CLI flags want their plain ASCII exactly as typed. And if your content pipeline uses straight quotes as data (CSV files, JSON, HTML attributes), the conversion must stay away from it. The rule of thumb: normalize at the last responsible moment, on finished human-facing text, and review anything structural afterwards.

Try it yourself

Paste a paragraph of straight-quoted draft text into the Typography Normalizer and watch the change counts — quotes, apostrophes, dashes and ellipsis are reported separately, so you can see exactly what your draft was missing. If you publish through a web page, the same characters appear in HTML source as entities; How HTML Entities Work explains why “ and — exist. And when you are doing a broader cleanup pass, Text Cleanup Pipeline shows where a typography pass fits alongside whitespace and case fixes.

Frequently asked questions

What is the difference between a hyphen, an en dash and an em dash?
The hyphen (-) joins words: well-known. The en dash (–, n-width) spans ranges like 10–20 and, spaced, marks asides. The em dash (—, m-width) makes a sentence-level interruption. They are three different characters, not three sizes of one.
Does converting to curly quotes break anything?
It breaks code and URLs: curly quotes are not string delimiters in most languages and a curly quote in a URL is a different character. Convert finished prose only, and keep normalizers away from source, config and CSV.
Why use the ellipsis character instead of three periods?
The … glyph is one unbreakable unit with even spacing, so lines cannot wrap between the dots, and search, screen readers and string comparisons treat it as one character rather than three.
Why did straight quotes become the default?
ASCII 1963 had one quote character and one hyphen because typewriters did. Plain-text files inherited those compromises, and keyboards still print straight quotes today — which is why conversion happens after typing, not during.