Fossil SCM
Expanded on the rules for literal/verbatim/fenced text in the /md_rules document.
Commit
1b2d6c30ba1ab06b64e9d88186895389c2129119b00ee8d887bbff5b6d3e9d9b
Parent
950e54ef35f61b3…
1 file changed
+24
-2
+24
-2
| --- src/markdown.md | ||
| +++ src/markdown.md | ||
| @@ -76,12 +76,34 @@ | ||
| 76 | 76 | > > |
| 77 | 77 | > This paragraph is indented |
| 78 | 78 | > > |
| 79 | 79 | > > Double-indented paragraph |
| 80 | 80 | |
| 81 | -> Begin each line with at least four spaces or one tab to produce a verbatim | |
| 82 | -> code block. | |
| 81 | +## Literal/Verbatim Text ## | |
| 82 | + | |
| 83 | +> There are several ways to write text in Markdown that should be | |
| 84 | +> rendered without any special interpretation. | |
| 85 | + | |
| 86 | +> For inline text, you can either use \``backticks`\` or the HTML | |
| 87 | +> `<code>` tag. | |
| 88 | +> | |
| 89 | +> For blocks of text, there are several methods: | |
| 90 | +> | |
| 91 | +> 1. Indent the text using a tab character or at least four spaces. | |
| 92 | +> 2. Precede the block with an HTML `<pre>` tag and follow it with `</pre>`. | |
| 93 | +> 3. Surround the block in triple backticks (\`\`\`) either at the | |
| 94 | +> left margin or indented no more than three spaces. | |
| 95 | + | |
| 96 | +> Note that unlike in [GitHub-Flavored Markdown][gfm], Fossil does not | |
| 97 | +> currently support any “info string” in [fenced code blocks][gfmf] | |
| 98 | +> after the opening sequence, including language tags | |
| 99 | + | |
| 100 | +> With the standard skins, verbatim text is rendered in a fixed-width font, | |
| 101 | +> but that is purely a presentation matter, controlled by the skin’s CSS. | |
| 102 | + | |
| 103 | +[gfm]: https://github.github.com/gfm/ | |
| 104 | +[gfmf]: https://github.github.com/gfm/#fenced-code-blocks | |
| 83 | 105 | |
| 84 | 106 | ## Tables ## |
| 85 | 107 | |
| 86 | 108 | > |
| 87 | 109 | | Header 1 | Header 2 | Header 3 | |
| 88 | 110 |
| --- src/markdown.md | |
| +++ src/markdown.md | |
| @@ -76,12 +76,34 @@ | |
| 76 | > > |
| 77 | > This paragraph is indented |
| 78 | > > |
| 79 | > > Double-indented paragraph |
| 80 | |
| 81 | > Begin each line with at least four spaces or one tab to produce a verbatim |
| 82 | > code block. |
| 83 | |
| 84 | ## Tables ## |
| 85 | |
| 86 | > |
| 87 | | Header 1 | Header 2 | Header 3 | |
| 88 |
| --- src/markdown.md | |
| +++ src/markdown.md | |
| @@ -76,12 +76,34 @@ | |
| 76 | > > |
| 77 | > This paragraph is indented |
| 78 | > > |
| 79 | > > Double-indented paragraph |
| 80 | |
| 81 | ## Literal/Verbatim Text ## |
| 82 | |
| 83 | > There are several ways to write text in Markdown that should be |
| 84 | > rendered without any special interpretation. |
| 85 | |
| 86 | > For inline text, you can either use \``backticks`\` or the HTML |
| 87 | > `<code>` tag. |
| 88 | > |
| 89 | > For blocks of text, there are several methods: |
| 90 | > |
| 91 | > 1. Indent the text using a tab character or at least four spaces. |
| 92 | > 2. Precede the block with an HTML `<pre>` tag and follow it with `</pre>`. |
| 93 | > 3. Surround the block in triple backticks (\`\`\`) either at the |
| 94 | > left margin or indented no more than three spaces. |
| 95 | |
| 96 | > Note that unlike in [GitHub-Flavored Markdown][gfm], Fossil does not |
| 97 | > currently support any “info string” in [fenced code blocks][gfmf] |
| 98 | > after the opening sequence, including language tags |
| 99 | |
| 100 | > With the standard skins, verbatim text is rendered in a fixed-width font, |
| 101 | > but that is purely a presentation matter, controlled by the skin’s CSS. |
| 102 | |
| 103 | [gfm]: https://github.github.com/gfm/ |
| 104 | [gfmf]: https://github.github.com/gfm/#fenced-code-blocks |
| 105 | |
| 106 | ## Tables ## |
| 107 | |
| 108 | > |
| 109 | | Header 1 | Header 2 | Header 3 | |
| 110 |