Markdown — render preview
Use this preview to compare the Markdown you enter with the final rendered message. The preview reflects how supported formatting appears in Output Messenger.
Supported markers
Markdown Text
Formatted Result
*bold*
bold
_italic_
italic
~strike~
strike
`inline code`
inline code“`block of code“`
block of codeCombined & in a real sentence
Please review the *deploy script* and run `npm test` before _Friday_.
Please review the deploy script and run npm test before Friday.~Old plan cancelled~ — *new plan* is live
Old plan cancelled— new plan is live
Intentionally NOT formatted (boundary rules)
I write C# and 2 * 3 = 6
I write C# and 2 * 3 = 6✓ left as typed
open my_file_name.txt
open my_file_name.txt✓ left as typed
use **double stars**
use **double stars**✗ Formatting is not applied
How raw text is preserved. When (and only when) markdown actually changes the text, the renderer stamps the original body onto the message
<pre data-md="…">. Every “give me the original text” path prefers data-md:- Copy (whole message & Copy Last Message) → clipboard gets
*bold*, notbold. - Forward → re-sends
*bold*; the recipient’s client renders it. - Edit → composer repopulates with
*bold*so re-sending never corrupts the message. - Partial text selection copy → intentionally returns the rendered (marker-stripped) text.
- Plain messages (no markers) carry no
data-mdand behave exactly as before.
