Destination formatting
Format cleaned text for email, messages, blogs, and documents
Cleaning and destination formatting answer different questions. Cleaning decides which artifacts should be removed. Destination formatting decides how the remaining structure should be represented when copied into email, messaging, a blog editor, a document, or a plain-text field.
TextClean parses a small semantic document model before rendering the destination. That lets one cleaned source retain headings, paragraphs, quotations, lists, and code without imposing a font or visual theme.
Before
# Update **Status:** ready - First item - Second item
After
Update Status: ready • First item • Second item
Start with semantic blocks
The renderer identifies Markdown headings, blank-line-separated paragraphs, block quotations, ordered and unordered lists, and fenced code. Ordinary lines remain together as a paragraph. Inline links, emphasis, and code can be represented in HTML or stripped for plain output.
This is intentionally smaller than a full Markdown specification. Predictable common structures are safer than pretending to parse every extension.
Email and document output
Email output includes both plain text and a simple HTML fragment. It uses headings, paragraphs, lists, quotations, and code elements without hard-coded fonts. The receiving mail application can apply its own typography.
Document output uses the same semantic HTML body. The file workspace can also export supported structure to DOCX, Markdown, HTML, or text.
Messages and plain text
Messaging applications vary widely. Bullets and paragraph spacing are more portable than elaborate indentation or embedded styling. Plain-text output removes inline Markdown markers while retaining hierarchy through spacing and list prefixes.
A destination can still collapse blank lines or restyle pasted content. Preview the final paste instead of assuming that the clipboard representation will be honoured.
Blog output and safe HTML
Blog output wraps the semantic body in an article element. Text is escaped before supported inline formatting is added, and generated links receive safe relationship attributes. This reduces the risk of pasted text becoming executable markup.
The fragment is suitable for copying into a compatible editor, but a publishing system may still filter elements or apply its own rules. Check the preview, links, headings, and code before publication.
Check before using the result
- Heading hierarchy
- List numbering and bullets
- Quotation boundaries
- Code and literal symbols
- The actual destination preview