Right Raised Omission Bracket ⸍

⸍ (U+2E0D) is a standard Unicode character that you can copy and paste anywhere text is accepted. This page provides a concise reference with safe tips, internal links, and practical guidance so you can use it reliably across apps and platforms.

What it is and where it’s used: Right Raised Omission Bracket is part of the Symbols family (block: Supplemental Punctuation). If you need styled or decorative alternatives, try our Fancy Text tool to generate compatible text that works in most modern interfaces.

History & usage: RIGHT RAISED OMISSION BRACKET (U+2E0D) is a punctuation mark in the Supplemental Punctuation block. It is a right raised variant used to indicate omitted text or to close a group that is skipped, depending on style. In use, brackets and quotes delimit groups, parameters, or quoted text in writing and code. This symbol helps mark the end of a skipped portion in a quotation or a code snippet, providing a visual cue for readers and programmers. It sits with other punctuation that guides how content is read and interpreted, especially when handling compact notations, lists, or embedded data. As a Unicode character, it supports international text work and mixed scripts, where clear delimitation of groups or quoted material matters for clarity. The history of such marks shows a move toward precise, machine readable punctuation that aids both human readers and software parsers. Today, writers and developers may use this gate-like symbol to signal omission or closure in tight examples, notes, or parameter lists, keeping syntax consistent across disciplines.

Copy and input: the quickest method is to copy the character here. You can also insert it by its codepoint U+2E0D in many development tools or editors. Some operating systems provide a character viewer or input palette that lets you search by name or code and insert the glyph into documents.

Display and fallback: if you see an empty box (tofu) or a placeholder rectangle, the active font might not include this codepoint. Switching to a font with broader Unicode coverage or using a fallback font usually fixes the issue. On the web, ensure the page’s font stack includes a general‑purpose fallback.

Related references: browse the Categories for similar characters. When choosing a symbol, prefer the official codepoint for semantic clarity and better compatibility with search, copy, and accessibility tooling.

See our category page for related symbols.