Closed msmid closed 9 years ago
In inline phase, I need to get rid of these "\"
Also, note that < or > will need special treatment (and others html-specific chars)
Works nicely but following structure *\*\*hello\*\**
may produce <em>**hello**</em>
, but it is ***hello***
instead.
Parsed characters are "taken" out of text for further parsing, so it is imposible for following functions to identify * text *
markup.
Another thing is that this parsing should be invoked after codespan parsing
Analyze string was responsible for above bug, now I use replace function, which has downfall too. It must unescape characters after all other parsing, because unescaped char is still char and can be parsed as markdown.
Now it is the very last step. Parsing spans and codespans however can't recognize escaped chars and therefore using escaped like \*
around these ones produce bugs.
Markdown supports escaping of characters including those which are used for mark up.
\ backslash ` backtick
hash mark