All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

RFC 454545: Proposed Standard for Proper Em Dash Usage in Technical Documentation

By

jdauriemma

2mo ago· 11 min readenCode

Summary

RFC 454545 is a fictional technical standard proposal that humorously addresses the misuse of em dashes in technical documentation. The document presents a formal RFC-style specification for proper em dash usage, including definitions, syntax, semantics, and implementation guidelines. It critiques common errors like using multiple hyphens instead of proper em dashes and provides detailed rules for spacing, length, and contextual usage. The RFC includes examples of correct and incorrect usage, implementation considerations for different platforms, and a formal ABNF grammar for em dash parsing. The document serves as both a technical specification and a satirical commentary on documentation quality.

Key quotes

· 5 pulled
The em dash (—) is a punctuation mark used to indicate a break in thought, an interruption, or to set off parenthetical information. It is distinct from the hyphen (-) and en dash (–) in both appearance and usage.
Common errors include using two hyphens (--) or three hyphens (---) in place of a proper em dash, inconsistent spacing around em dashes, and using em dashes where other punctuation would be more appropriate.
This document defines a standard for the proper use of em dashes in technical documentation, with the goal of improving readability, consistency, and professionalism in RFCs, API documentation, and other technical writing.
Implementations MUST support the Unicode character U+2014 (EM DASH) as the canonical representation. Fallback mechanisms MAY include conversion from double hyphens (--) or triple hyphens (---) when proper em dash characters are not available.
The em dash standard is not merely about typography—it is about clarity of communication. Proper punctuation helps readers understand technical concepts without unnecessary cognitive load.
Snippet from the RSS feed
GitHub Gist: instantly share code, notes, and snippets.

You might also wanna read