Smart punctuation vs ASCII: when plain text is the better choice
Curly quotes, em dashes, ellipses, and other smart punctuation are not automatically bad. They become a problem when text leaves a styled editor and moves into markdown, code comments, feeds, support systems, or other channels that reward predictable ASCII.
Key takeaways
- Typography is a style decision in publishing, but a compatibility decision in plain-text systems.
- ASCII is safer when the destination strips formatting, runs validation, or passes content through scripts and older tools.
- The best cleanup flow is not 'replace everything.' It is 'normalize the safe parts, then review the ambiguous ones.'
What counts as smart punctuation
The usual set includes curly quotes, smart apostrophes, en dashes, em dashes, ellipsis characters, guillemets, and language-specific punctuation marks that look polished in a rich editor.
These characters can be perfectly legitimate in a typeset article or a polished PDF. They become risky when you need portability, consistent encoding, or simple character-level comparisons.
When ASCII wins
ASCII is the safer default in markdown, terminals, changelogs, code blocks, spreadsheet exports, CLI tooling, product feeds, and CMS inputs that may pass through multiple sanitizers. In those environments, a straight quote or hyphen is usually more valuable than typographic finesse.
ASCII also helps teams who move text through many systems in a row. The goal is not to make everything ugly. The goal is to keep the same characters behaving the same way from editor to editor.
- Use ASCII in technical docs, code-adjacent text, prompts, and structured content fields.
- Keep smart punctuation in editorial or print contexts where typographic tone matters.
- Review em dashes and language-specific punctuation manually instead of flattening them by habit.
A practical review rule
If the destination is plain, automated, or strict, normalize. If the destination is human-first, polished, and typography-aware, keep the original punctuation when it is intentional.
That simple rule prevents two common mistakes: over-cleaning writing that is supposed to feel editorial, and under-cleaning writing that is about to move through brittle technical systems.