What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 129 Stack Exchange communities.

Possible Duplicate:
Preview should match the posted view

look this question: firefox: don't save error pages in history

I wrote inside something like this notbold**bold**.notbold.

In javascript it is rendered ok, but in the server, instead the asterisks are shown and the text is not bolded.

share|improve this question

marked as duplicate by Joel Coehoorn Sep 14 '09 at 13:00

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

1  
"Possible duplicate" post does not exist anymore. –  Artemix Aug 12 '13 at 11:36

2 Answers 2

This is by design and explained on the blog in the episode entitled, "Three Markdown Gotchas"

1) Markdown’s single biggest flaw is its intra-word emphasis.

I don’t think anybody writes:

un*fricking*believable

often enough to justify making it nearly impossible to talk about tokens with underscores in them:

some_file_name

is interpreted as:

some<em>file</em>name

It even works across word boundaries:

file_one and file_two

becomes:

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 a*b*c, 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.

Basically, if you want to have italics or bold markup in the middle of your words, you're going to have to whip out the HTML tags and tag them up that style.

Basically, if you want to have i<i>tal</i>ics or bold markup 
in the mi<b>dd</b>le of your words, you're going to have to 
whip out the HTML tags and tag them up that style.
share|improve this answer
    
th<b>an</b>k you –  flybywire Sep 13 '09 at 10:24
6  
Yeah, but don't count that on working in comments. –  random Sep 13 '09 at 10:32
    
th*an*k you? –  deleted Sep 13 '09 at 21:54
1  
"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." -- Yeah, that's why you should use real, consistent markup. Real, consistent markup doesn't have edge cases. –  Svante Oct 23 '09 at 9:58

As I see it, the problem isn't so much that mark down is finicky about intra-word emphasis. The problem is that it looks okay in the preview and doesn't break until after you click "post". But in any case, it's dupe:

http://meta.stackexchange.com/questions/1227/preview-should-match-the-posted-view

share|improve this answer
    
meta.stackexchange.com/questions/4286 :-) –  balpha Sep 14 '09 at 13:39

Not the answer you're looking for? Browse other questions tagged .