").str(elt.contents.str).s("")
191 | case HTML:
192 | s = elt.contents.str
193 | case LINK:
194 | o := w.obfuscate
195 | if strings.Index(elt.contents.link.url, "mailto:") == 0 {
196 | w.obfuscate = true /* obfuscate mailto: links */
197 | }
198 | w.s(` 0 {
200 | w.s(` title="`).str(elt.contents.link.title).s(`"`)
201 | }
202 | w.s(">").elist(elt.contents.link.label).s("")
203 | w.obfuscate = o
204 | case IMAGE:
205 | w.s(`", elt) 229 | case HRULE: 230 | w.sp().s("
") 231 | case HTMLBLOCK: 232 | w.sp().s(elt.contents.str) 233 | case VERBATIM: 234 | w.sp().s("
").str(elt.contents.str).s("- ", elt)
237 | case ORDEREDLIST:
238 | w.listBlock("
- ", elt) 243 | case DEFDATA: 244 | w.listItem("
- ", elt)
245 | case LISTITEM:
246 | w.listItem("
- ", elt) 247 | case BLOCKQUOTE: 248 | w.sp().s("
\n").skipPadding().children(elt).br().s("
") 249 | case REFERENCE: 250 | /* Nonprinting */ 251 | case NOTE: 252 | /* if contents.str == 0, then print note; else ignore, since this 253 | * is a note block that has been incorporated into the notes list 254 | */ 255 | if elt.contents.str == "" { 256 | w.endNotes = append(w.endNotes, elt) /* add an endnote to global endnotes list */ 257 | w.notenum++ 258 | nn := w.notenum 259 | s = fmt.Sprintf(`[%d]`, 260 | nn, nn, nn, nn) 261 | } 262 | default: 263 | log.Fatalf("htmlOut.elem encountered unknown element key = %d\n", elt.key) 264 | } 265 | if s != "" { 266 | w.s(s) 267 | } 268 | return w 269 | } 270 | 271 | func (w *htmlOut) printEndnotes() { 272 | extraNewline := func() { 273 | // add an extra newline to maintain 274 | // compatibility with the C version. 275 | w.padded-- 276 | } 277 | 278 | counter := 0 279 | 280 | w.s("
\n- ")
281 | for _, elt := range w.endNotes {
282 | counter++
283 | extraNewline()
284 | w.br().s(fmt.Sprintf("
- \n", counter)).skipPadding() 285 | w.children(elt) 286 | w.s(fmt.Sprintf(" [back]", counter)) 287 | w.br().s(" ") 288 | } 289 | extraNewline() 290 | w.br().s("
Here is a footnote reference,[1] and another.[2]
2 | 3 |This paragraph won't be part of the note, because it 4 | isn't indented.
5 | 6 |
7 |-
8 |
9 |
-
10 |
Here is the footnote.
[back] 11 |
12 |
13 | -
14 |
Here's one with multiple blocks.
15 | 16 |Subsequent paragraphs are indented to show that they 17 | belong to the previous footnote.
18 | 19 |
21 | 22 |{ some.code } 20 |The whole paragraph can be indented, or just the first 23 | line. In this way, multi-paragraph footnotes work like 24 | multi-paragraph list items.
[back] 25 |
26 |
27 |
AT&T has an ampersand in their name.
2 | 3 |AT&T is another way to write it.
4 | 5 |This & that.
6 | 7 |4 < 5.
8 | 9 |6 > 5.
10 | 11 |Here's a link with an ampersand in the URL.
12 | 13 |Here's a link with an amersand in the link text: AT&T.
14 | 15 |Here's an inline link.
16 | 17 |Here's an inline link.
18 | -------------------------------------------------------------------------------- /tests/md1.0.3/Amps and angle encoding.mm: -------------------------------------------------------------------------------- 1 | .P 2 | AT&T has an ampersand in their name. 3 | .P 4 | ATT is another way to write it. 5 | .P 6 | This & that. 7 | .P 8 | 4 < 5. 9 | .P 10 | 6 > 5. 11 | .P 12 | Here's a link (http://example.com/?foo=1&bar=2) with an ampersand in the URL. 13 | .P 14 | Here's a link with an amersand in the link text: AT&T (http://att.com/)\[char46] 15 | .P 16 | Here's an inline link (/script?foo=1&bar=2)\[char46] 17 | .P 18 | Here's an inline link (/script?foo=1&bar=2)\[char46] 19 | -------------------------------------------------------------------------------- /tests/md1.0.3/Amps and angle encoding.text: -------------------------------------------------------------------------------- 1 | AT&T has an ampersand in their name. 2 | 3 | AT&T is another way to write it. 4 | 5 | This & that. 6 | 7 | 4 < 5. 8 | 9 | 6 > 5. 10 | 11 | Here's a [link] [1] with an ampersand in the URL. 12 | 13 | Here's a link with an amersand in the link text: [AT&T] [2]. 14 | 15 | Here's an inline [link](/script?foo=1&bar=2). 16 | 17 | Here's an inline [link](). 18 | 19 | 20 | [1]: http://example.com/?foo=1&bar=2 21 | [2]: http://att.com/ "AT&T" -------------------------------------------------------------------------------- /tests/md1.0.3/Auto links.html: -------------------------------------------------------------------------------- 1 |Link: http://example.com/.
2 | 3 |With an ampersand: http://example.com/?foo=1&bar=2
4 | 5 |-
6 |
- In a list? 7 |
- http://example.com/ 8 |
- It should. 9 |
12 |
14 | 15 |Blockquoted: http://example.com/
13 |Auto-links should not occur here:
16 | 17 |<http://example.com/>
19 | -------------------------------------------------------------------------------- /tests/md1.0.3/Auto links.mm: -------------------------------------------------------------------------------- 1 | .P 2 | Link: http://example.com/ (http://example.com/)\[char46] 3 | .P 4 | With an ampersand: http://example.com/?foo=1&bar=2 (http://example.com/?foo=1&bar=2) 5 | .BL 6 | .LI 7 | In a list? 8 | .LI 9 | http://example.com/ (http://example.com/) 10 | .LI 11 | It should. 12 | .LE 1 13 | .DS I 14 | .P 15 | Blockquoted: http://example.com/ (http://example.com/) 16 | .DE 17 | .P 18 | Auto-links should not occur here: \fCor here: <http://example.com/> 18 |These should all get escaped:
2 | 3 |Backslash: \
4 | 5 |Backtick: `
6 | 7 |Asterisk: *
8 | 9 |Underscore: _
10 | 11 |Left brace: {
12 | 13 |Right brace: }
14 | 15 |Left bracket: [
16 | 17 |Right bracket: ]
18 | 19 |Left paren: (
20 | 21 |Right paren: )
22 | 23 |Greater-than: >
24 | 25 |Hash: #
26 | 27 |Period: .
28 | 29 |Bang: !
30 | 31 |Plus: +
32 | 33 |Minus: -
34 | 35 |These should not, because they occur within a code block:
36 | 37 |
69 | 70 |Backslash: \\ 38 | 39 | Backtick: \` 40 | 41 | Asterisk: \* 42 | 43 | Underscore: \_ 44 | 45 | Left brace: \{ 46 | 47 | Right brace: \} 48 | 49 | Left bracket: \[ 50 | 51 | Right bracket: \] 52 | 53 | Left paren: \( 54 | 55 | Right paren: \) 56 | 57 | Greater-than: \> 58 | 59 | Hash: \# 60 | 61 | Period: \. 62 | 63 | Bang: \! 64 | 65 | Plus: \+ 66 | 67 | Minus: \- 68 |Nor should these, which occur in code spans:
71 | 72 |Backslash:
73 | 74 |\\Backtick:
75 | 76 |\`Asterisk:
77 | 78 |\*Underscore:
79 | 80 |\_Left brace:
81 | 82 |\{Right brace:
83 | 84 |\}Left bracket:
85 | 86 |\[Right bracket:
87 | 88 |\]Left paren:
89 | 90 |\(Right paren:
91 | 92 |\)Greater-than:
93 | 94 |\>Hash:
95 | 96 |\#Period:
97 | 98 |\.Bang:
99 | 100 |\!Plus:
101 | 102 |\+Minus:
103 | 104 |\-These should get escaped, even though they're matching pairs for 105 | other Markdown constructs:
106 | 107 |*asterisks*
108 | 109 |_underscores_
110 | 111 |`backticks`
112 | 113 |This is a code span with a literal backslash-backtick sequence:
114 | 115 |\`This is a tag with unescaped backticks bar.
116 | 117 |This is a tag with backslashes bar.
118 | -------------------------------------------------------------------------------- /tests/md1.0.3/Backslash escapes.mm: -------------------------------------------------------------------------------- 1 | .P 2 | These should all get escaped: 3 | .P 4 | Backslash: \e 5 | .P 6 | Backtick: ` 7 | .P 8 | Asterisk: * 9 | .P 10 | Underscore: _ 11 | .P 12 | Left brace: { 13 | .P 14 | Right brace: } 15 | .P 16 | Left bracket: [ 17 | .P 18 | Right bracket: ] 19 | .P 20 | Left paren: ( 21 | .P 22 | Right paren: ) 23 | .P 24 | Greater-than: > 25 | .P 26 | Hash: # 27 | .P 28 | Period: \[char46] 29 | .P 30 | Bang: ! 31 | .P 32 | Plus: + 33 | .P 34 | Minus: - 35 | .P 36 | These should not, because they occur within a code block: 37 | .VERBON 2 38 | Backslash: \e\e 39 | 40 | Backtick: \e` 41 | 42 | Asterisk: \e* 43 | 44 | Underscore: \e_ 45 | 46 | Left brace: \e{ 47 | 48 | Right brace: \e} 49 | 50 | Left bracket: \e[ 51 | 52 | Right bracket: \e] 53 | 54 | Left paren: \e( 55 | 56 | Right paren: \e) 57 | 58 | Greater-than: \e> 59 | 60 | Hash: \e# 61 | 62 | Period: \e. 63 | 64 | Bang: \e! 65 | 66 | Plus: \e+ 67 | 68 | Minus: \e- 69 | .VERBOFF 70 | .P 71 | Nor should these, which occur in code spans: 72 | .P 73 | Backslash: \fC\e\e\fR 74 | .P 75 | Backtick: \fC\e`\fR 76 | .P 77 | Asterisk: \fC\e*\fR 78 | .P 79 | Underscore: \fC\e_\fR 80 | .P 81 | Left brace: \fC\e{\fR 82 | .P 83 | Right brace: \fC\e}\fR 84 | .P 85 | Left bracket: \fC\e[\fR 86 | .P 87 | Right bracket: \fC\e]\fR 88 | .P 89 | Left paren: \fC\e(\fR 90 | .P 91 | Right paren: \fC\e)\fR 92 | .P 93 | Greater-than: \fC\e>\fR 94 | .P 95 | Hash: \fC\e#\fR 96 | .P 97 | Period: \fC\e.\fR 98 | .P 99 | Bang: \fC\e!\fR 100 | .P 101 | Plus: \fC\e+\fR 102 | .P 103 | Minus: \fC\e-\fR 104 | .P 105 | These should get escaped, even though they're matching pairs for 106 | other Markdown constructs: 107 | .P 108 | *asterisks* 109 | .P 110 | _underscores_ 111 | .P 112 | `backticks` 113 | .P 114 | This is a code span with a literal backslash-backtick sequence: \fC\e`\fR 115 | .P 116 | This is a tag with unescaped backticks bar\[char46] 117 | .P 118 | This is a tag with backslashes bar\[char46] 119 | -------------------------------------------------------------------------------- /tests/md1.0.3/Backslash escapes.text: -------------------------------------------------------------------------------- 1 | These should all get escaped: 2 | 3 | Backslash: \\ 4 | 5 | Backtick: \` 6 | 7 | Asterisk: \* 8 | 9 | Underscore: \_ 10 | 11 | Left brace: \{ 12 | 13 | Right brace: \} 14 | 15 | Left bracket: \[ 16 | 17 | Right bracket: \] 18 | 19 | Left paren: \( 20 | 21 | Right paren: \) 22 | 23 | Greater-than: \> 24 | 25 | Hash: \# 26 | 27 | Period: \. 28 | 29 | Bang: \! 30 | 31 | Plus: \+ 32 | 33 | Minus: \- 34 | 35 | 36 | 37 | These should not, because they occur within a code block: 38 | 39 | Backslash: \\ 40 | 41 | Backtick: \` 42 | 43 | Asterisk: \* 44 | 45 | Underscore: \_ 46 | 47 | Left brace: \{ 48 | 49 | Right brace: \} 50 | 51 | Left bracket: \[ 52 | 53 | Right bracket: \] 54 | 55 | Left paren: \( 56 | 57 | Right paren: \) 58 | 59 | Greater-than: \> 60 | 61 | Hash: \# 62 | 63 | Period: \. 64 | 65 | Bang: \! 66 | 67 | Plus: \+ 68 | 69 | Minus: \- 70 | 71 | 72 | Nor should these, which occur in code spans: 73 | 74 | Backslash: `\\` 75 | 76 | Backtick: `` \` `` 77 | 78 | Asterisk: `\*` 79 | 80 | Underscore: `\_` 81 | 82 | Left brace: `\{` 83 | 84 | Right brace: `\}` 85 | 86 | Left bracket: `\[` 87 | 88 | Right bracket: `\]` 89 | 90 | Left paren: `\(` 91 | 92 | Right paren: `\)` 93 | 94 | Greater-than: `\>` 95 | 96 | Hash: `\#` 97 | 98 | Period: `\.` 99 | 100 | Bang: `\!` 101 | 102 | Plus: `\+` 103 | 104 | Minus: `\-` 105 | 106 | 107 | These should get escaped, even though they're matching pairs for 108 | other Markdown constructs: 109 | 110 | \*asterisks\* 111 | 112 | \_underscores\_ 113 | 114 | \`backticks\` 115 | 116 | This is a code span with a literal backslash-backtick sequence: `` \` `` 117 | 118 | This is a tag with unescaped backticks bar. 119 | 120 | This is a tag with backslashes bar. 121 | -------------------------------------------------------------------------------- /tests/md1.0.3/Blockquotes with code blocks.html: -------------------------------------------------------------------------------- 1 |2 |
16 | -------------------------------------------------------------------------------- /tests/md1.0.3/Blockquotes with code blocks.mm: -------------------------------------------------------------------------------- 1 | .DS I 2 | .P 3 | Example: 4 | .VERBON 2 5 | sub status { 6 | print "working"; 7 | } 8 | .VERBOFF 9 | .P 10 | Or: 11 | .VERBON 2 12 | sub status { 13 | return "working"; 14 | } 15 | .VERBOFF 16 | .DE 17 | -------------------------------------------------------------------------------- /tests/md1.0.3/Blockquotes with code blocks.text: -------------------------------------------------------------------------------- 1 | > Example: 2 | > 3 | > sub status { 4 | > print "working"; 5 | > } 6 | > 7 | > Or: 8 | > 9 | > sub status { 10 | > return "working"; 11 | > } 12 | -------------------------------------------------------------------------------- /tests/md1.0.3/Code Blocks.html: -------------------------------------------------------------------------------- 1 |Example:
3 | 4 |
8 | 9 |sub status { 5 | print "working"; 6 | } 7 |Or:
10 | 11 |
15 |sub status { 12 | return "working"; 13 | } 14 |
3 | 4 |code block on the first line 2 |Regular text.
5 | 6 |
8 | 9 |code block indented by spaces 7 |Regular text.
10 | 11 |
14 | 15 |the lines in this block 12 | all contain trailing spaces 13 |Regular Text.
16 | 17 |
19 | -------------------------------------------------------------------------------- /tests/md1.0.3/Code Blocks.mm: -------------------------------------------------------------------------------- 1 | .VERBON 2 2 | code block on the first line 3 | .VERBOFF 4 | .P 5 | Regular text. 6 | .VERBON 2 7 | code block indented by spaces 8 | .VERBOFF 9 | .P 10 | Regular text. 11 | .VERBON 2 12 | the lines in this block 13 | all contain trailing spaces 14 | .VERBOFF 15 | .P 16 | Regular Text. 17 | .VERBON 2 18 | code block on the last line 19 | .VERBOFF 20 | -------------------------------------------------------------------------------- /tests/md1.0.3/Code Blocks.text: -------------------------------------------------------------------------------- 1 | code block on the first line 2 | 3 | Regular text. 4 | 5 | code block indented by spaces 6 | 7 | Regular text. 8 | 9 | the lines in this block 10 | all contain trailing spaces 11 | 12 | Regular Text. 13 | 14 | code block on the last line -------------------------------------------------------------------------------- /tests/md1.0.3/Code Spans.html: -------------------------------------------------------------------------------- 1 |code block on the last line 18 |
2 | 3 |<test a="content of attribute">Fix for backticks within HTML tag: like this
4 | 5 |Here's how you put
6 | -------------------------------------------------------------------------------- /tests/md1.0.3/Code Spans.mm: -------------------------------------------------------------------------------- 1 | .P 2 | \fC`backticks`in a code span.\fR 3 | .P 4 | Fix for backticks within HTML tag: like this 5 | .P 6 | Here's how you put \fC`backticks`\fR in a code span. 7 | -------------------------------------------------------------------------------- /tests/md1.0.3/Code Spans.text: -------------------------------------------------------------------------------- 1 | ` ` 2 | 3 | Fix for backticks within HTML tag: like this 4 | 5 | Here's how you put `` `backticks` `` in a code span. 6 | 7 | -------------------------------------------------------------------------------- /tests/md1.0.3/Hard-wrapped paragraphs with list-like lines.html: -------------------------------------------------------------------------------- 1 | In Markdown 1.0.0 and earlier. Version 2 | 8. This line turns into a list item. 3 | Because a hard-wrapped line in the 4 | middle of a paragraph looked like a 5 | list item.
6 | 7 |Here's one with a bullet. 8 | * criminey.
9 | -------------------------------------------------------------------------------- /tests/md1.0.3/Hard-wrapped paragraphs with list-like lines.mm: -------------------------------------------------------------------------------- 1 | .P 2 | In Markdown 1.0.0 and earlier. Version 3 | 8. This line turns into a list item. 4 | Because a hard-wrapped line in the 5 | middle of a paragraph looked like a 6 | list item. 7 | .P 8 | Here's one with a bullet. 9 | * criminey. 10 | -------------------------------------------------------------------------------- /tests/md1.0.3/Hard-wrapped paragraphs with list-like lines.text: -------------------------------------------------------------------------------- 1 | In Markdown 1.0.0 and earlier. Version 2 | 8. This line turns into a list item. 3 | Because a hard-wrapped line in the 4 | middle of a paragraph looked like a 5 | list item. 6 | 7 | Here's one with a bullet. 8 | * criminey. 9 | -------------------------------------------------------------------------------- /tests/md1.0.3/Horizontal rules.html: -------------------------------------------------------------------------------- 1 |Dashes:
2 | 3 |
4 | 5 |
6 | 7 |
8 | 9 |
10 | 11 |
13 | 14 |--- 12 |
15 | 16 |
17 | 18 |
19 | 20 |
21 | 22 |
24 | 25 |- - - 23 |Asterisks:
26 | 27 |
28 | 29 |
30 | 31 |
32 | 33 |
34 | 35 |
37 | 38 |*** 36 |
39 | 40 |
41 | 42 |
43 | 44 |
45 | 46 |
48 | 49 |* * * 47 |Underscores:
50 | 51 |
52 | 53 |
54 | 55 |
56 | 57 |
58 | 59 |
61 | 62 |___ 60 |
63 | 64 |
65 | 66 |
67 | 68 |
69 | 70 |
72 | -------------------------------------------------------------------------------- /tests/md1.0.3/Horizontal rules.mm: -------------------------------------------------------------------------------- 1 | .P 2 | Dashes: 3 | \l'\n(.lu*8u/10u' 4 | \l'\n(.lu*8u/10u' 5 | \l'\n(.lu*8u/10u' 6 | \l'\n(.lu*8u/10u' 7 | .VERBON 2 8 | --- 9 | .VERBOFF 10 | \l'\n(.lu*8u/10u' 11 | \l'\n(.lu*8u/10u' 12 | \l'\n(.lu*8u/10u' 13 | \l'\n(.lu*8u/10u' 14 | .VERBON 2 15 | - - - 16 | .VERBOFF 17 | .P 18 | Asterisks: 19 | \l'\n(.lu*8u/10u' 20 | \l'\n(.lu*8u/10u' 21 | \l'\n(.lu*8u/10u' 22 | \l'\n(.lu*8u/10u' 23 | .VERBON 2 24 | *** 25 | .VERBOFF 26 | \l'\n(.lu*8u/10u' 27 | \l'\n(.lu*8u/10u' 28 | \l'\n(.lu*8u/10u' 29 | \l'\n(.lu*8u/10u' 30 | .VERBON 2 31 | * * * 32 | .VERBOFF 33 | .P 34 | Underscores: 35 | \l'\n(.lu*8u/10u' 36 | \l'\n(.lu*8u/10u' 37 | \l'\n(.lu*8u/10u' 38 | \l'\n(.lu*8u/10u' 39 | .VERBON 2 40 | ___ 41 | .VERBOFF 42 | \l'\n(.lu*8u/10u' 43 | \l'\n(.lu*8u/10u' 44 | \l'\n(.lu*8u/10u' 45 | \l'\n(.lu*8u/10u' 46 | .VERBON 2 47 | _ _ _ 48 | .VERBOFF 49 | -------------------------------------------------------------------------------- /tests/md1.0.3/Horizontal rules.text: -------------------------------------------------------------------------------- 1 | Dashes: 2 | 3 | --- 4 | 5 | --- 6 | 7 | --- 8 | 9 | --- 10 | 11 | --- 12 | 13 | - - - 14 | 15 | - - - 16 | 17 | - - - 18 | 19 | - - - 20 | 21 | - - - 22 | 23 | 24 | Asterisks: 25 | 26 | *** 27 | 28 | *** 29 | 30 | *** 31 | 32 | *** 33 | 34 | *** 35 | 36 | * * * 37 | 38 | * * * 39 | 40 | * * * 41 | 42 | * * * 43 | 44 | * * * 45 | 46 | 47 | Underscores: 48 | 49 | ___ 50 | 51 | ___ 52 | 53 | ___ 54 | 55 | ___ 56 | 57 | ___ 58 | 59 | _ _ _ 60 | 61 | _ _ _ 62 | 63 | _ _ _ 64 | 65 | _ _ _ 66 | 67 | _ _ _ 68 | -------------------------------------------------------------------------------- /tests/md1.0.3/Inline HTML (Advanced).html: -------------------------------------------------------------------------------- 1 |_ _ _ 71 |Simple block on one line:
2 | 3 |foo4 | 5 |And nested without indentation:
6 | 7 |8 |16 | -------------------------------------------------------------------------------- /tests/md1.0.3/Inline HTML (Advanced).mm: -------------------------------------------------------------------------------- 1 | .P 2 | Simple block on one line: 3 | .P 4 | And nested without indentation: 5 | -------------------------------------------------------------------------------- /tests/md1.0.3/Inline HTML (Advanced).text: -------------------------------------------------------------------------------- 1 | Simple block on one line: 2 | 3 |9 |14 |10 | foo 11 |12 | 13 |bar15 |foo4 | 5 | And nested without indentation: 6 | 7 |8 |16 | -------------------------------------------------------------------------------- /tests/md1.0.3/Inline HTML (Simple).html: -------------------------------------------------------------------------------- 1 |9 |14 |10 | foo 11 |12 | 13 |bar15 |Here's a simple block:
2 | 3 |4 | foo 5 |6 | 7 |This should be a code block, though:
8 | 9 |
13 | 14 |<div> 10 | foo 11 | </div> 12 |As should this:
15 | 16 |
18 | 19 |<div>foo</div> 17 |Now, nested:
20 | 21 |22 |28 | 29 |23 |27 |24 | foo 25 |26 |This should just be an HTML comment:
30 | 31 | 32 | 33 |Multiline:
34 | 35 | 39 | 40 |Code block:
41 | 42 |
44 | 45 |<!-- Comment --> 43 |Just plain comment, with trailing spaces on the line:
46 | 47 | 48 | 49 |Code:
50 | 51 |
53 | 54 |<hr /> 52 |Hr's:
55 | 56 |
57 | 58 |
59 | 60 |
61 | 62 |
63 | 64 |
65 | 66 |
67 | 68 |
69 | 70 |
71 | 72 |
73 | -------------------------------------------------------------------------------- /tests/md1.0.3/Inline HTML (Simple).mm: -------------------------------------------------------------------------------- 1 | .P 2 | Here's a simple block: 3 | .P 4 | This should be a code block, though: 5 | .VERBON 2 6 |7 | foo 8 |9 | .VERBOFF 10 | .P 11 | As should this: 12 | .VERBON 2 13 |foo14 | .VERBOFF 15 | .P 16 | Now, nested: 17 | .P 18 | This should just be an HTML comment: 19 | .P 20 | Multiline: 21 | .P 22 | Code block: 23 | .VERBON 2 24 | 25 | .VERBOFF 26 | .P 27 | Just plain comment, with trailing spaces on the line: 28 | .P 29 | Code: 30 | .VERBON 2 31 |
32 | .VERBOFF 33 | .P 34 | Hr's: 35 | .P 36 | 37 | .P 38 | 39 | .P 40 | 41 | -------------------------------------------------------------------------------- /tests/md1.0.3/Inline HTML (Simple).text: -------------------------------------------------------------------------------- 1 | Here's a simple block: 2 | 3 |4 | foo 5 |6 | 7 | This should be a code block, though: 8 | 9 |10 | foo 11 |12 | 13 | As should this: 14 | 15 |foo16 | 17 | Now, nested: 18 | 19 |20 |26 | 27 | This should just be an HTML comment: 28 | 29 | 30 | 31 | Multiline: 32 | 33 | 37 | 38 | Code block: 39 | 40 | 41 | 42 | Just plain comment, with trailing spaces on the line: 43 | 44 | 45 | 46 | Code: 47 | 48 |21 |25 |22 | foo 23 |24 |
49 | 50 | Hr's: 51 | 52 |
53 | 54 |
55 | 56 |
57 | 58 |
59 | 60 |
61 | 62 |
63 | 64 |
65 | 66 |
67 | 68 |
69 | 70 | -------------------------------------------------------------------------------- /tests/md1.0.3/Inline HTML comments.html: -------------------------------------------------------------------------------- 1 |Paragraph one.
2 | 3 | 4 | 5 | 8 | 9 |Paragraph two.
10 | 11 | 12 | 13 |The end.
14 | -------------------------------------------------------------------------------- /tests/md1.0.3/Inline HTML comments.mm: -------------------------------------------------------------------------------- 1 | .P 2 | Paragraph one. 3 | .P 4 | Paragraph two. 5 | .P 6 | The end. 7 | -------------------------------------------------------------------------------- /tests/md1.0.3/Inline HTML comments.text: -------------------------------------------------------------------------------- 1 | Paragraph one. 2 | 3 | 4 | 5 | 8 | 9 | Paragraph two. 10 | 11 | 12 | 13 | The end. 14 | -------------------------------------------------------------------------------- /tests/md1.0.3/Links, inline style.mm: -------------------------------------------------------------------------------- 1 | .P 2 | Just a URL (/url/)\[char46] 3 | .P 4 | URL and title (/url/)\[char46] 5 | .P 6 | URL and title (/url/)\[char46] 7 | .P 8 | URL and title (/url/)\[char46] 9 | .P 10 | URL and title (/url/)\[char46] 11 | .P 12 | Empty ()\[char46] 13 | -------------------------------------------------------------------------------- /tests/md1.0.3/Links, reference style.mm: -------------------------------------------------------------------------------- 1 | .P 2 | Foo bar (/url/)\[char46] 3 | .P 4 | Foo bar (/url/)\[char46] 5 | .P 6 | Foo bar (/url/)\[char46] 7 | .P 8 | With embedded [brackets] (/url/)\[char46] 9 | .P 10 | Indented once (/url)\[char46] 11 | .P 12 | Indented twice (/url)\[char46] 13 | .P 14 | Indented thrice (/url)\[char46] 15 | .P 16 | Indented [four][] times. 17 | .VERBON 2 18 | [four]: /url 19 | .VERBOFF 20 | \l'\n(.lu*8u/10u' 21 | .P 22 | this (foo) should work 23 | .P 24 | So should this (foo)\[char46] 25 | .P 26 | And this (foo)\[char46] 27 | .P 28 | And this (foo)\[char46] 29 | .P 30 | And this (foo)\[char46] 31 | .P 32 | But not [that] []\[char46] 33 | .P 34 | Nor [that][]\[char46] 35 | .P 36 | Nor [that]\[char46] 37 | .P 38 | [Something in brackets like this (foo) should work] 39 | .P 40 | [Same with this (foo)\[char46]] 41 | .P 42 | In this case, this (/somethingelse/) points to something else. 43 | .P 44 | Backslashing should suppress [this] and [this]\[char46] 45 | \l'\n(.lu*8u/10u' 46 | .P 47 | Here's one where the link 48 | breaks (/url/) across lines. 49 | .P 50 | Here's another where the link 51 | breaks (/url/) across lines, but with a line-ending space. 52 | -------------------------------------------------------------------------------- /tests/md1.0.3/Links, shortcut references.mm: -------------------------------------------------------------------------------- 1 | .P 2 | This is the simple case (/simple)\[char46] 3 | .P 4 | This one has a line 5 | break (/foo)\[char46] 6 | .P 7 | This one has a line 8 | break (/foo) with a line-ending space. 9 | .P 10 | this (/that) and the other (/other) 11 | -------------------------------------------------------------------------------- /tests/md1.0.3/Literal quotes in titles.html: -------------------------------------------------------------------------------- 1 |Foo bar.
2 | 3 |Foo bar.
4 | -------------------------------------------------------------------------------- /tests/md1.0.3/Literal quotes in titles.mm: -------------------------------------------------------------------------------- 1 | .P 2 | Foo bar (/url/)\[char46] 3 | .P 4 | Foo bar (/url/)\[char46] 5 | -------------------------------------------------------------------------------- /tests/md1.0.3/Literal quotes in titles.text: -------------------------------------------------------------------------------- 1 | Foo [bar][]. 2 | 3 | Foo [bar](/url/ "Title with "quotes" inside"). 4 | 5 | 6 | [bar]: /url/ "Title with "quotes" inside" 7 | 8 | -------------------------------------------------------------------------------- /tests/md1.0.3/Markdown Documentation - Basics.html: -------------------------------------------------------------------------------- 1 |Markdown: Basics
2 | 3 | 10 | 11 |Getting the Gist of Markdown's Formatting Syntax
12 | 13 |This page offers a brief overview of what it's like to use Markdown. 14 | The syntax page provides complete, detailed documentation for 15 | every feature, but Markdown should be very easy to pick up simply by 16 | looking at a few examples of it in action. The examples on this page 17 | are written in a before/after style, showing example syntax and the 18 | HTML output produced by Markdown.
19 | 20 |It's also helpful to simply try Markdown out; the Dingus is a 21 | web application that allows you type your own Markdown-formatted text 22 | and translate it to XHTML.
23 | 24 |Note: This document is itself written using Markdown; you 25 | can see the source for it by adding '.text' to the URL.
26 | 27 |Paragraphs, Headers, Blockquotes
28 | 29 |A paragraph is simply one or more consecutive lines of text, separated 30 | by one or more blank lines. (A blank line is any line that looks like a 31 | blank line -- a line containing nothing spaces or tabs is considered 32 | blank.) Normal paragraphs should not be intended with spaces or tabs.
33 | 34 |Markdown offers two styles of headers: Setext and atx. 35 | Setext-style headers for
40 | 41 |<h1>and<h2>are created by 36 | "underlining" with equal signs (=) and hyphens (-), respectively. 37 | To create an atx-style header, you put 1-6 hash marks (#) at the 38 | beginning of the line -- the number of hashes equals the resulting 39 | HTML header level.Blockquotes are indicated using email-style '
42 | 43 |>' angle brackets.Markdown:
44 | 45 |
66 | 67 |A First Level Header 46 | ==================== 47 | 48 | A Second Level Header 49 | --------------------- 50 | 51 | Now is the time for all good men to come to 52 | the aid of their country. This is just a 53 | regular paragraph. 54 | 55 | The quick brown fox jumped over the lazy 56 | dog's back. 57 | 58 | ### Header 3 59 | 60 | > This is a blockquote. 61 | > 62 | > This is the second paragraph in the blockquote. 63 | > 64 | > ## This is an H2 in a blockquote 65 |Output:
68 | 69 |
90 | 91 |<h1>A First Level Header</h1> 70 | 71 | <h2>A Second Level Header</h2> 72 | 73 | <p>Now is the time for all good men to come to 74 | the aid of their country. This is just a 75 | regular paragraph.</p> 76 | 77 | <p>The quick brown fox jumped over the lazy 78 | dog's back.</p> 79 | 80 | <h3>Header 3</h3> 81 | 82 | <blockquote> 83 | <p>This is a blockquote.</p> 84 | 85 | <p>This is the second paragraph in the blockquote.</p> 86 | 87 | <h2>This is an H2 in a blockquote</h2> 88 | </blockquote> 89 |Phrase Emphasis
92 | 93 |Markdown uses asterisks and underscores to indicate spans of emphasis.
94 | 95 |Markdown:
96 | 97 |
103 | 104 |Some of these words *are emphasized*. 98 | Some of these words _are emphasized also_. 99 | 100 | Use two asterisks for **strong emphasis**. 101 | Or, if you prefer, __use two underscores instead__. 102 |Output:
105 | 106 |
112 | 113 |<p>Some of these words <em>are emphasized</em>. 107 | Some of these words <em>are emphasized also</em>.</p> 108 | 109 | <p>Use two asterisks for <strong>strong emphasis</strong>. 110 | Or, if you prefer, <strong>use two underscores instead</strong>.</p> 111 |Lists
114 | 115 |Unordered (bulleted) lists use asterisks, pluses, and hyphens (
118 | 119 |*, 116 |+, and-) as list markers. These three markers are 117 | interchangable; this:
123 | 124 |* Candy. 120 | * Gum. 121 | * Booze. 122 |this:
125 | 126 |
130 | 131 |+ Candy. 127 | + Gum. 128 | + Booze. 129 |and this:
132 | 133 |
137 | 138 |- Candy. 134 | - Gum. 135 | - Booze. 136 |all produce the same output:
139 | 140 |
146 | 147 |<ul> 141 | <li>Candy.</li> 142 | <li>Gum.</li> 143 | <li>Booze.</li> 144 | </ul> 145 |Ordered (numbered) lists use regular numbers, followed by periods, as 148 | list markers:
149 | 150 |
154 | 155 |1. Red 151 | 2. Green 152 | 3. Blue 153 |Output:
156 | 157 |
163 | 164 |<ol> 158 | <li>Red</li> 159 | <li>Green</li> 160 | <li>Blue</li> 161 | </ol> 162 |If you put blank lines between items, you'll get
167 | 168 |<p>tags for the 165 | list item text. You can create multi-paragraph list items by indenting 166 | the paragraphs by 4 spaces or 1 tab:
174 | 175 |* A list item. 169 | 170 | With multiple paragraphs. 171 | 172 | * Another item in the list. 173 |Output:
176 | 177 |
183 | 184 |<ul> 178 | <li><p>A list item.</p> 179 | <p>With multiple paragraphs.</p></li> 180 | <li><p>Another item in the list.</p></li> 181 | </ul> 182 |Links
185 | 186 |Markdown supports two styles for creating links: inline and 187 | reference. With both styles, you use square brackets to delimit the 188 | text you want to turn into a link.
189 | 190 |Inline-style links use parentheses immediately after the link text. 191 | For example:
192 | 193 |
195 | 196 |This is an [example link](http://example.com/). 194 |Output:
197 | 198 |
201 | 202 |<p>This is an <a href="http://example.com/"> 199 | example link</a>.</p> 200 |Optionally, you may include a title attribute in the parentheses:
203 | 204 |
206 | 207 |This is an [example link](http://example.com/ "With a Title"). 205 |Output:
208 | 209 |
212 | 213 |<p>This is an <a href="http://example.com/" title="With a Title"> 210 | example link</a>.</p> 211 |Reference-style links allow you to refer to your links by names, which 214 | you define elsewhere in your document:
215 | 216 |
223 | 224 |I get 10 times more traffic from [Google][1] than from 217 | [Yahoo][2] or [MSN][3]. 218 | 219 | [1]: http://google.com/ "Google" 220 | [2]: http://search.yahoo.com/ "Yahoo Search" 221 | [3]: http://search.msn.com/ "MSN Search" 222 |Output:
225 | 226 |
231 | 232 |<p>I get 10 times more traffic from <a href="http://google.com/" 227 | title="Google">Google</a> than from <a href="http://search.yahoo.com/" 228 | title="Yahoo Search">Yahoo</a> or <a href="http://search.msn.com/" 229 | title="MSN Search">MSN</a>.</p> 230 |The title attribute is optional. Link names may contain letters, 233 | numbers and spaces, but are not case sensitive:
234 | 235 |
240 | 241 |I start my morning with a cup of coffee and 236 | [The New York Times][NY Times]. 237 | 238 | [ny times]: http://www.nytimes.com/ 239 |Output:
242 | 243 |
246 | 247 |<p>I start my morning with a cup of coffee and 244 | <a href="http://www.nytimes.com/">The New York Times</a>.</p> 245 |Images
248 | 249 |Image syntax is very much like link syntax.
250 | 251 |Inline (titles are optional):
252 | 253 |
255 | 256 | 254 |Reference-style:
257 | 258 |
262 | 263 |![alt text][id] 259 | 260 | [id]: /path/to/img.jpg "Title" 261 |Both of the above examples produce the same output:
264 | 265 |
267 | 268 |<img src="/path/to/img.jpg" alt="alt text" title="Title" /> 266 |Code
269 | 270 |In a regular paragraph, you can create code span by wrapping text in 271 | backtick quotes. Any ampersands (
274 | 275 |&) and angle brackets (<or 272 |>) will automatically be translated into HTML entities. This makes 273 | it easy to use Markdown to write about HTML example code:
280 | 281 |I strongly recommend against using any `<blink>` tags. 276 | 277 | I wish SmartyPants used named entities like `—` 278 | instead of decimal-encoded entites like `—`. 279 |Output:
282 | 283 |
290 | 291 |<p>I strongly recommend against using any 284 | <code><blink></code> tags.</p> 285 | 286 | <p>I wish SmartyPants used named entities like 287 | <code>&mdash;</code> instead of decimal-encoded 288 | entites like <code>&#8212;</code>.</p> 289 |To specify an entire block of pre-formatted code, indent every line of 292 | the block by 4 spaces or 1 tab. Just like with code spans,
294 | 295 |&,<, 293 | and>characters will be escaped automatically.Markdown:
296 | 297 |
304 | 305 |If you want your page to validate under XHTML 1.0 Strict, 298 | you've got to put paragraph tags in your blockquotes: 299 | 300 | <blockquote> 301 | <p>For example.</p> 302 | </blockquote> 303 |Output:
306 | 307 |
315 | -------------------------------------------------------------------------------- /tests/md1.0.3/Markdown Documentation - Basics.mm: -------------------------------------------------------------------------------- 1 | .H 1 "Markdown: Basics" 2 | .H 2 "Getting the Gist of Markdown's Formatting Syntax" 3 | .P 4 | This page offers a brief overview of what it's like to use Markdown. 5 | The syntax page (/projects/markdown/syntax) provides complete, detailed documentation for 6 | every feature, but Markdown should be very easy to pick up simply by 7 | looking at a few examples of it in action. The examples on this page 8 | are written in a before/after style, showing example syntax and the 9 | HTML output produced by Markdown. 10 | .P 11 | It's also helpful to simply try Markdown out; the Dingus (/projects/markdown/dingus) is a 12 | web application that allows you type your own Markdown-formatted text 13 | and translate it to XHTML. 14 | .P 15 | \fBNote:\fR This document is itself written using Markdown; you 16 | can see the source for it by adding '\[char46]text' to the URL (/projects/markdown/basics.text)\[char46] 17 | .H 2 "Paragraphs, Headers, Blockquotes" 18 | .P 19 | A paragraph is simply one or more consecutive lines of text, separated 20 | by one or more blank lines. (A blank line is any line that looks like a 21 | blank line -- a line containing nothing spaces or tabs is considered 22 | blank.) Normal paragraphs should not be intended with spaces or tabs. 23 | .P 24 | Markdown offers two styles of headers: \fISetext\fR and \fIatx\fR\[char46] 25 | Setext-style headers for \fC<p>If you want your page to validate under XHTML 1.0 Strict, 308 | you've got to put paragraph tags in your blockquotes:</p> 309 | 310 | <pre><code><blockquote> 311 | <p>For example.</p> 312 | </blockquote> 313 | </code></pre> 314 |\fR and \fC
\fR are created by 26 | "underlining" with equal signs (\fC=\fR) and hyphens (\fC-\fR), respectively. 27 | To create an atx-style header, you put 1-6 hash marks (\fC#\fR) at the 28 | beginning of the line -- the number of hashes equals the resulting 29 | HTML header level. 30 | .P 31 | Blockquotes are indicated using email-style '\fC>\fR' angle brackets. 32 | .P 33 | Markdown: 34 | .VERBON 2 35 | A First Level Header 36 | ==================== 37 | 38 | A Second Level Header 39 | --------------------- 40 | 41 | Now is the time for all good men to come to 42 | the aid of their country. This is just a 43 | regular paragraph. 44 | 45 | The quick brown fox jumped over the lazy 46 | dog's back. 47 | 48 | ### Header 3 49 | 50 | > This is a blockquote. 51 | > 52 | > This is the second paragraph in the blockquote. 53 | > 54 | > ## This is an H2 in a blockquote 55 | .VERBOFF 56 | .P 57 | Output: 58 | .VERBON 2 59 |
A First Level Header
60 | 61 |A Second Level Header
62 | 63 |Now is the time for all good men to come to 64 | the aid of their country. This is just a 65 | regular paragraph.
66 | 67 |The quick brown fox jumped over the lazy 68 | dog's back.
69 | 70 |Header 3
71 | 72 |73 |
79 | .VERBOFF 80 | .H 3 "Phrase Emphasis" 81 | .P 82 | Markdown uses asterisks and underscores to indicate spans of emphasis. 83 | .P 84 | Markdown: 85 | .VERBON 2 86 | Some of these words *are emphasized*. 87 | Some of these words _are emphasized also_. 88 | 89 | Use two asterisks for **strong emphasis**. 90 | Or, if you prefer, __use two underscores instead__. 91 | .VERBOFF 92 | .P 93 | Output: 94 | .VERBON 2 95 |This is a blockquote.
74 | 75 |This is the second paragraph in the blockquote.
76 | 77 |This is an H2 in a blockquote
78 |Some of these words are emphasized. 96 | Some of these words are emphasized also.
97 | 98 |Use two asterisks for strong emphasis. 99 | Or, if you prefer, use two underscores instead.
100 | .VERBOFF 101 | .H 2 "Lists" 102 | .P 103 | Unordered (bulleted) lists use asterisks, pluses, and hyphens (\fC*\fR, 104 | \fC+\fR, and \fC-\fR) as list markers. These three markers are 105 | interchangable; this: 106 | .VERBON 2 107 | * Candy. 108 | * Gum. 109 | * Booze. 110 | .VERBOFF 111 | .P 112 | this: 113 | .VERBON 2 114 | + Candy. 115 | + Gum. 116 | + Booze. 117 | .VERBOFF 118 | .P 119 | and this: 120 | .VERBON 2 121 | - Candy. 122 | - Gum. 123 | - Booze. 124 | .VERBOFF 125 | .P 126 | all produce the same output: 127 | .VERBON 2 128 |-
129 |
- Candy. 130 |
- Gum. 131 |
- Booze. 132 |
-
146 |
- Red 147 |
- Green 148 |
- Blue 149 |
\fR tags for the 153 | list item text. You can create multi-paragraph list items by indenting 154 | the paragraphs by 4 spaces or 1 tab: 155 | .VERBON 2 156 | * A list item. 157 | 158 | With multiple paragraphs. 159 | 160 | * Another item in the list. 161 | .VERBOFF 162 | .P 163 | Output: 164 | .VERBON 2 165 |
-
166 |
A list item.
167 |With multiple paragraphs.
168 | Another item in the list.
169 |
This is an 186 | example link.
187 | .VERBOFF 188 | .P 189 | Optionally, you may include a title attribute in the parentheses: 190 | .VERBON 2 191 | This is an [example link](http://example.com/ "With a Title"). 192 | .VERBOFF 193 | .P 194 | Output: 195 | .VERBON 2 196 |This is an 197 | example link.
198 | .VERBOFF 199 | .P 200 | Reference-style links allow you to refer to your links by names, which 201 | you define elsewhere in your document: 202 | .VERBON 2 203 | I get 10 times more traffic from [Google][1] than from 204 | [Yahoo][2] or [MSN][3]. 205 | 206 | [1]: http://google.com/ "Google" 207 | [2]: http://search.yahoo.com/ "Yahoo Search" 208 | [3]: http://search.msn.com/ "MSN Search" 209 | .VERBOFF 210 | .P 211 | Output: 212 | .VERBON 2 213 |I get 10 times more traffic from Google than from Yahoo or MSN.
217 | .VERBOFF 218 | .P 219 | The title attribute is optional. Link names may contain letters, 220 | numbers and spaces, but are \fInot\fR case sensitive: 221 | .VERBON 2 222 | I start my morning with a cup of coffee and 223 | [The New York Times][NY Times]. 224 | 225 | [ny times]: http://www.nytimes.com/ 226 | .VERBOFF 227 | .P 228 | Output: 229 | .VERBON 2 230 |I start my morning with a cup of coffee and 231 | The New York Times.
232 | .VERBOFF 233 | .H 3 "Images" 234 | .P 235 | Image syntax is very much like link syntax. 236 | .P 237 | Inline (titles are optional): 238 | .VERBON 2 239 |  240 | .VERBOFF 241 | .P 242 | Reference-style: 243 | .VERBON 2 244 | ![alt text][id] 245 | 246 | [id]: /path/to/img.jpg "Title" 247 | .VERBOFF 248 | .P 249 | Both of the above examples produce the same output: 250 | .VERBON 2 251 |
252 | .VERBOFF
253 | .H 3 "Code"
254 | .P
255 | In a regular paragraph, you can create code span by wrapping text in
256 | backtick quotes. Any ampersands (\fC&\fR) and angle brackets (\fC<\fR or
257 | \fC>\fR) will automatically be translated into HTML entities. This makes
258 | it easy to use Markdown to write about HTML example code:
259 | .VERBON 2
260 | I strongly recommend against using any ` - ", elt) 247 | case BLOCKQUOTE: 248 | w.sp().s("
- ", elt)
239 | case DEFINITIONLIST:
240 | w.listBlock("
- ", elt)
241 | case DEFTITLE:
242 | w.listItem("