Unicode Punctuation for Writers: Ellipsis, Copyright, and Other Symbols

Most writers know the basics of punctuation from school: periods, commas, question marks, exclamation points. A smaller group has mastered the em dash and the smart quote. But there is a whole tier of typographic symbols that professional writers, editors, ebook publishers, and content creators encounter regularly — symbols that look simple but carry specific technical and legal meanings, and that can cause unexpected problems when encoding goes wrong.

This guide covers the Unicode characters that matter most for writers who publish content on the web, in ebooks, or in professional documents.

The Ellipsis: One Character, Not Three

This is one of the most common typographic misunderstandings in digital writing. When a writer wants to indicate a pause, a trailing off of thought, or an omission in a quote, they type three periods: ...

That produces three separate characters — three U+002E FULL STOP characters — not a typographic ellipsis.

The Unicode ellipsis is a single character: … (U+2026, HORIZONTAL ELLIPSIS).

Why It Matters

Visual consistency: In a professional font, the Unicode ellipsis character is designed with specific, even spacing between the three dots. Three typed periods use whatever letter-spacing the font applies, which may look slightly different.

Line breaking: Three separate periods can potentially be broken across two lines by a text renderer, particularly in narrow columns or mobile viewports. A single ellipsis character stays together because it is a single unit.

Character count: In environments where character count matters — Twitter/X used to count the ellipsis as one character when typed as U+2026, versus three characters when typed as three periods — the single character is more efficient.

Semantic precision: In formal editing and academic writing, the treatment of ellipsis is codified. The Chicago Manual of Style specifies that an omission within a sentence uses three spaced periods (…) while an omission at the end of a sentence uses a fourth period for the sentence full stop (… .). Most digital publishing uses the simpler single-character ellipsis, but knowing the distinction matters for formal work.

Search and processing: Some text processing tools, search engines, and database queries handle the Unicode ellipsis character differently from three periods. If you are using regular expressions to process text, \.\.\. matches three literal periods but will not match U+2026.

To type the ellipsis character: on macOS, use Option + ;. On Windows, use Alt + 0133 on the numeric keypad. In HTML, use … or …. In Markdown processed by most static site generators, three dots in prose context are rendered as three periods; you may need to paste the Unicode character directly if you want the single-character version.

Copyright ©, Registered ®, and Trademark ™

These three symbols appear constantly in commercial writing, product descriptions, legal copy, and brand documentation. Understanding their meanings prevents legal errors and sloppy writing.

Copyright © (U+00A9)

The copyright symbol indicates that a work is protected by copyright law. In most countries that have signed the Berne Convention, copyright protection is automatic from the moment of creation and does not require registration or the use of the symbol. However, displaying the copyright notice serves as a public declaration of ownership and is required to maintain certain legal remedies in some jurisdictions.

A standard copyright notice looks like: © 2026 Your Name or Company. All rights reserved.

The “All rights reserved” phrase is a legacy of older international copyright treaties and is no longer legally required in most countries, but it remains common in professional publishing.

Registered Trademark ® (U+00AE)

The ® symbol means the trademark has been officially registered with a government trademark office — in the United States, the USPTO (United States Patent and Trademark Office). Only registered trademarks may use this symbol. Using ® on an unregistered mark is a misrepresentation that can create legal liability.

Registration provides stronger legal protections than an unregistered mark, including the right to sue in federal court, the ability to block infringing imports, and nationwide presumption of ownership.

Trademark ™ (U+2122)

The ™ symbol indicates a claim of trademark rights in a name, logo, or phrase, even without formal registration. Any business can use ™ to signal a trademark claim — no government filing is required. It provides weaker protection than ® but still establishes a public record of the claim and may deter infringers.

Common use: a company launching a new product might use ™ immediately while the registration application is pending, then switch to ® once the mark is officially registered.

Typing These Symbols

For bulk content that contains many instances of (c), (r), and (tm) — as often happens when editing legal documents, product catalogs, or brand guidelines — the Smart Quotes Formatter can convert these ASCII shorthands to proper Unicode symbols throughout your entire document in one operation.

Non-Breaking Space (U+00A0)

The non-breaking space is an invisible formatting character that looks identical to a regular space but tells the text renderer never to break the line at that point. It is one of the most practically useful Unicode characters for writers who care about how their text renders.

When to Use It

Numbers with units: 10 kg, 5 MB, 3.5 miles, $12 million. Without a non-breaking space, these can split across lines so that the number is on one line and the unit is on the next — which looks wrong and is harder to read.

Titles and names: Mr. Smith, Dr. Jones, St. Paul, No. 5. The title should always stay with the name it precedes.

Chapter and section references: Chapter 3, Section 12, Figure 4. The word and the number should not be separated.

Abbreviations followed by a specific item: vol. 3, p. 47, op. cit.

Currencies with amounts: € 50, $ 1,000 (when currency symbol and amount are styled with a space between them, as some typographic conventions require).

In HTML, the non-breaking space entity is   — you have certainly seen this in HTML source code. In most word processors and page layout applications, you can insert it directly. In plain-text writing that will be processed into HTML, you may need to insert the character itself or use a find-and-replace step.

How to Type It

• macOS: Option + Space
• Windows: Alt + 0160
• HTML:   or  
• CSS alternative: For web content, white-space: nowrap on an inline element achieves a similar result without modifying the text itself.

The Prime Symbol ′ vs the Apostrophe ’

Here is a distinction that most writers — and many editors — completely miss.

The apostrophe (', U+2019, or the straight version ', U+0027) is a punctuation mark used for contractions and possessives in text. It is not the correct character for measurements.

The prime symbol (′, U+2032) is the correct character for expressing measurements in feet, arcminutes, and minutes of time. The double prime (″, U+2033) is correct for inches, arcseconds, and seconds of time.

Correct: He is 5′ 10″ tall. Common but typographically incorrect: He is 5’ 10” tall. (using apostrophe and straight double quote)

This distinction matters most in technical writing, scientific content, architectural plans, and formal measurements. In casual prose, the apostrophe and straight quote are widely used for this purpose and are rarely criticized.

Why Copy-Pasting from Word Breaks Typography

If you have ever copy-pasted content from a Microsoft Word document into a CMS (WordPress, Webflow, Contentful, Notion, etc.) and found that your curly quotes appeared as “, â€, or ‘ — or as question marks in boxes — you have encountered an encoding mismatch.

Here is what happens technically:

1. Microsoft Word saves documents internally using Windows-1252 encoding (a superset of Latin-1), in which curly quotes have specific byte values: the left double quote is byte 0x93 and the right double quote is byte 0x94.
2. When you copy text from Word and paste it into a system that interprets text as UTF-8, those byte values are decoded under UTF-8 rules — but 0x93 and 0x94 are not valid single-byte characters in UTF-8. The decoder produces replacement characters or garbled output.

The same issue affects em dashes, en dashes, ellipses, and any typographic character that lives outside plain ASCII.

How to Prevent Encoding Problems

Ensure UTF-8 throughout your pipeline. Your text editor should save files in UTF-8. Your database should use UTF-8 collation (utf8mb4 in MySQL). Your server should send Content-Type: text/html; charset=UTF-8 headers.

Use HTML entities for critical symbols. If you are uncertain about your encoding pipeline, use HTML entities instead of Unicode characters directly: “ and ” for curly double quotes, — for em dash, … for ellipsis. Entities are pure ASCII and cannot be garbled by encoding mismatches.

Paste as plain text first. Many CMSs allow you to paste as plain text (often Ctrl+Shift+V or a dedicated “Paste as plain text” button). This strips all Word formatting, including the encoded typographic characters, giving you a clean starting point with straight ASCII quotes and hyphens that you can then convert properly.

Use a dedicated conversion tool. Run your text through Smart Quotes Formatter after pasting to ensure all typographic characters are properly applied as Unicode and not inherited from a potentially garbled Word paste.

UTF-8 vs HTML Entities for Web Publishing

When publishing to the web, you have two options for typographic characters: insert the Unicode character directly (e.g., —) or use an HTML entity (e.g., —).

Both are valid. Modern best practice favors direct Unicode characters because:

• Source code is more readable: She left—and never came back. is clearer than She left—and never came back.
• UTF-8 is universal: Every modern browser, server, and database supports UTF-8. The historic concern that some systems could not handle non-ASCII characters is no longer relevant.
• Less verbose: HTML entities add bytes to your page weight, and while the difference is tiny, Unicode characters are always shorter.

The case for HTML entities:

• Absolute encoding safety in legacy systems that might not properly declare or handle UTF-8.
• Useful in environments where you cannot control server headers or database encoding.
• Required by some older CMS templates or email marketing platforms.

For most writers in 2026 publishing to modern web platforms, using Unicode characters directly is the correct choice. If you are working with a legacy system and experiencing encoding issues, entities are a reliable fallback.

A Workflow for Clean Typography

Maintaining clean, consistent typographic punctuation across all your content does not require memorizing Unicode codepoints or mastering Alt codes. A practical workflow:

1. Draft freely in your preferred tool — plain text, Markdown, Google Docs, or a writing app. Use --- for em dash, -- for en dash, ... for ellipsis, (c) for copyright, " and ' for quotes. Focus on the words, not the characters.

2. Convert before publishing using Smart Quotes Formatter or a similar tool. In one pass, all your ASCII shorthands become proper Unicode typographic characters.

3. Review the output in context. Check that apostrophes in contractions are correct, that quotes are correctly directional, and that no unintended conversions occurred in code snippets or technical content.

4. Publish with confidence knowing your text uses proper Unicode characters that will render beautifully in browsers, e-readers, and print.

The characters covered in this guide — the ellipsis, the copyright and trademark symbols, the non-breaking space, the prime symbol — each solve a specific typographic problem. Knowing when to reach for them, and how to do so without interrupting your writing flow, is what separates text that looks polished from text that merely communicates. Both accomplish the job, but one does it with craft.