You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Will try to make markdown as a common syntax as it being the majority base syntax, and an attribute to specify whether the text should be in markdown-like format.
However Markdown is still less organised, and harder to escape compare to HTML (which has a relatively established standard for formatting). I'm still undecided about whether to use HTML or Markdown for this.
Looking for a general, easy to parse, convert and subset representation of rich text in text messages.
Rich text representation in some IMs:
Bold, italics, monospaced, monospaced block, link, strikethrough and underline, @ reference. Nesting supported.
(offset, length, attributes); Markdown subset; HTML subset;
Bold, italics, strikethrough, quote, inline code, block code, list, link, user&channel reference, etc. Nesting allowed.
mrkdwn
(variation of Markdown)Bold, italics, strikethrough, underline, inline code, code block, syntax highlighting, spoiler alerts. Nesting allowed.
Markdown subset.
None.
Bold, italic, strikethrough, monospace, codeblock, LaTeX (
\(\sin(2\pi)\)
).Web only.
Inline image, custom emoticon.
CoolQ token in messages.
Custom emoticon.
Unicode Private Use Area.
Bold, italics, strikethrough, monospaced, quote. Nesting allowed.
Markdown subset, extended. (XEP-0393)
None.
Bold, italic, strikethrough, inline code, image, link. Nesting allowed.
Markdown subset.
Bold, italic, strikethrough, inline code, code block.
Markdown-like.
The text was updated successfully, but these errors were encountered: