Parsedown does not escape * character inside of backticks

[ek68794998]

Note: Please see referenced issue.

If given the following input...

*(Test `a*b` test`.)*

... Parsedown will actually parse it into something like...

<i>(Test `a</i>b<code> test</code>.)*

Whereas it should be parsed into...

<i>(Test <code>a*b</code> test`.)</i>

This is in line with how, for example, GitHub renders it: (Test a*b test`.)

Here is a shot from the online Parsedown demo displaying the issue (thanks, @flaviocopes!):

[aidantwoods]

Among other things, noted here already 😉 #434 (see: "Issues elsewhere").

@erusev Parsedown will have to change its parsing strategy for inline elements to fix this one (assign priority to inline code – since escapes for most characters don't (and shouldn't) work there). Inline code is a bit of a special case when it comes to priority of inline markers – I think the order of first occurrence based approach is correct for other markers though.

In terms of correctness – I'm not even sure that the commonmark reference parser has been equipped to deal with some cases of element nesting ¯\_(ツ)_/¯

[ek68794998]

@aidantwoods Thanks for the link!

Looks like that bug has been open for around 3 months now. Is it being actively worked on?