Have a look at this answer
One of the bolds works, and the other one just turns up as ** in the actual post.
This is the string that isn't working:
Which renders as: xml nib
Meta Stack Exchange is a question and answer site for meta-discussion of the Stack Exchange family of Q&A websites. It only takes a minute to sign up.Sign up to join this community
This is not a bug; this is by design.
It becomes very difficult to talk about code when your_variable_names_are_suddenly_underlined. Intra-word emphasis is a bad idea and we have EXPLICITLY disabled it.
1) Markdown’s single biggest flaw is its intra-word emphasis.
I don’t think anybody writes:
often enough to justify making it nearly impossible to talk about tokens with underscores in them:
is interpreted as:
It even works across word boundaries:
file_one and file_two
file<em>one and file</em> two
Whenever you’re writing tokens with underscores you have to make absolutely sure you’re in a backtick-delimited code span. The same problem will also nail you on equations like abc, but that seems to pop up less frequently.
Showdown follows the reference implementation on all this, but in WMD I do a little preprocessing to hack the idiocy away: basically I just backslash-escape any underscores or asterisks that might trigger it. It’s a flagrant violation of the standard, but since it’s a pre-pass that should produce identical output with any Markdown processor, I feel justified. Unfortunately my hack did screw up one edge case (which I don’t have in front of me) and there isn’t any way to disable it. Both those things will change in the next release.
This used to be intentional for a long time, but now it works. See Markdown change: Intra-word emphasis now works.
Is a double asterisk a left bracket, or a right bracket, or a single asterisk that's been escaped? It gets worse. A single asterisk can be a left bracket or a right bracket as well. If I remember right, single asterisk indicates italics. No matter how you write the parser, there are going to be complaints.
This text was bracketed by single asterisks.
To see the problem more clearly, consider quoted text inside of CSV. A quote mark can be a left bracket or a right bracket. A double quote is typically an escaped single quote. Quotes cannot be nested.