Question

I am using MarkdownSharp in one of my projects and have noticed that if any of my Url’s contain pairs of underscore characters somewhere within it, it’s treated as italic and therefore replaces the _ with <em>.

I’ve had a look on google but can’t find any reference to this problem behaviour, and from reading some of the comments in the MarkdownSharp code, it suggests that the code is written the way it is to prevent this from happening. See below snippet from the markdown code:

The order in which other subs are called here is essential. Link and image substitutions need to happen before EscapeSpecialChars(), so that any *’s or _’s in the a and img tags get encoded.

    public string Transform(string text)
    {
        if (String.IsNullOrEmpty(text)) return "";

        Setup();

        text = Normalize(text);

        text = HashHTMLBlocks(text);
        text = StripLinkDefinitions(text);
        text = RunBlockGamut(text);
        text = Unescape(text);

        Cleanup();

        return text + "\n";
    }

Is there a known workaround for this behaviour?

** UPDATE: I have just tested entering a url on StackOverflow which I believe uses a version of MarkdownSharp (and AutoHyperlink is enabled as per my project) and whilst it handles a single underscore instance within the url, as soon as a pair of underscores appear in the url, it breaks.

Answer 1

Have you tried escaping the _ characters that you want to preserve by using a backslash?

See: http://daringfireball.net/projects/markdown/syntax#backslash

From the article:

For example, if you wanted to surround a word with literal asterisks (instead of an HTML <em> tag), you can use backslashes before the asterisks, like this:

\*literal asterisks\*

Asterisks in Markdown are more or less the same as underscores.

---

Edit: The answer was accepted due to this comment I made. The OP decided to disable auto hyperlinks and manually insert the links with either HTML markup or Markdown link syntax.

Sounds like that feature wasn’t thought through well enough. It comes with a warning saying it will make the system do things that aren’t compliant with standard markdown, which seems to me like a warning that they didn’t solve every problem with those features. You might need to change the library to fix bugs like that…