summaryrefslogtreecommitdiffstats
path: root/tdemarkdown/md4c/test/strikethrough.txt
blob: 884ce5983f90ee1b0c9d065131e3dd91422dbe76 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75

# Strike-Through

With the flag `MD_FLAG_STRIKETHROUGH`, MD4C enables extension for recognition
of strike-through spans.

Strike-through text is any text wrapped in one or two tildes (`~`).

```````````````````````````````` example
~Hi~ Hello, world!
.
<p><del>Hi</del> Hello, world!</p>
````````````````````````````````

If the length of the opener and closer doesn't match, the strike-through is
not recognized.

```````````````````````````````` example
This ~text~~ is curious.
.
<p>This ~text~~ is curious.</p>
````````````````````````````````

Too long tilde sequence won't be recognized:

```````````````````````````````` example
foo ~~~bar~~~
.
<p>foo ~~~bar~~~</p>
````````````````````````````````

Also note the markers cannot open a strike-through span if they are followed
with a whitespace; and similarly, then cannot close the span if they are
preceded with a whitespace:

```````````````````````````````` example
~foo ~bar
.
<p>~foo ~bar</p>
````````````````````````````````


As with regular emphasis delimiters, a new paragraph will cause the cessation
of parsing a strike-through:

```````````````````````````````` example
This ~~has a

new paragraph~~.
.
<p>This ~~has a</p>
<p>new paragraph~~.</p>
````````````````````````````````


## GitHub Issues

### [Issue 69](https://github.com/mity/md4c/issues/69)
```````````````````````````````` example
~`foo`~
.
<p><del><code>foo</code></del></p>
````````````````````````````````

```````````````````````````````` example
~*foo*~
.
<p><del><em>foo</em></del></p>
````````````````````````````````

```````````````````````````````` example
*~foo~*
.
<p><em><del>foo</del></em></p>
````````````````````````````````