For comparing supported formatting features between frontends.
Header 1
Header 2
Header 3
Header 4
This is normal text. Two spaces at end of line to force line break.
italic with underscores
italic with asterisks
bold with double asterisks
bold with double underscores
strikethrough with double tildes
superscriptwith-single-caret-no-spaces-or-nesting
subscriptwith-single-tilde-no-spaces-or-nesting
This is inline code with single backticks.
This is a code block
with triple backticks.
This is a code block
indented by 4 spaces.
Block quote
after paragraph break
Spoiler block with triple colons
Spoiler content
Jerboa test
1
12
123
1234
Apparently, some of the Markdown isn’t converted to Rich Text. I can still see it in the start post.
Strikethrough, superscript, subscript, code blocks and spoilers don’t work.
Are you using Jerboa to view this post? There are various issues on this, and this is also why I created this post.
E.g. the strikethrough thing should be fixed in the next release: https://github.com/dessalines/jerboa/pull/610
The spoiler issue is still open: https://github.com/dessalines/jerboa/issues/627
The markdown source of the above post:
# Header 1 ## Header 2 ### Header 3 #### Header 4 This is normal text. Two spaces at end of line to force line break. _italic with underscores_ *italic with asterisks* **bold with double asterisks** __bold with double underscores__ ~~strikethrough with double tildes~~ superscript^with-single-caret-no-spaces-or-nesting^ subscript~with-single-tilde-no-spaces-or-nesting~ This is `inline code` with single backticks. ``` This is a code block with triple backticks. ``` This is a code block indented by 4 spaces. > Block quote > > after paragraph break ::: spoiler Spoiler block with triple colons Spoiler content :::
