Inconsistent parsing of curly braces with special attributes enabled

[mathewinwood]

Handling of {} braces is inconsistent when special attributes are enabled. See test.md.txt for a repro case:

$ hoedown --special-attribute < ./test.md 

What I see is that in specific cases only, text within {...} is removed from the output, and replaced with this:

  </p>

  <p>

in the output. The exact same text inside {...} in other contexts is left unaffected in the outputted HTML. Again, see the repro case above.

What I've tried:

• Escaping all curly braces with \; this works in most cases, but in the problematic case all the text within the braces gets removed, and I see a single \ in the output. See this file (repro in the same way as above)
• If I add an empty {} immediately after the problem case, only these braces are removed and my output is as I expect
• If I add a single space after the closing } then the problem goes away. This is my workaround for the time being.

The fact that a single space fixes the issue makes me suspect a parsing issue. The problem does not repro without the --special-attribute flag.

Context: I have a documenation pipeline that combines markdown processing with javadoc, allowing me to write markdown formatted docs that can also link to generated Java docs using the standard javadoc {@link class.Name link} syntax.

[mathewinwood]

Thanks fox fixing!