Why do not use marked? It should better than showdown.

👍

@vilic Have you found a decent workaround for this in the meantime?

@tomekr sadly no.

I think this is showdownjs/showdown#208 and there's an easy solution.

@jgillich I can get the work around you posted to work on http://showdownjs.github.io but not in Ghost. The best I've been able to manage is:

1. item one
    ```code 1
    code 2
    ```
2. item two

Which creates what looks like a code block broken in half over two lines:

@JohnWestlund I believe the workaround doesn't used "fenced" code blocks, rather relies on the indentation to indicate a code block. e.g.:

@kevinansfield yes, the indentation work but how do you use syntax highlight without fenced code blocks

 ```language-javascript
 [...]
 ```

How about this?

Code blocks nested in blockquote are not rendered correctly. It should be a <pre><code>...</code></pre>, but in Ghost got just <code>。

Take below as example:

> Note:
>
> Some code in blockquote.
>
> ```javascript
> function() {
>   consoel.log('hello world!');
> }
> ```

This block is rendered to:

<blockquote>
  <p>Note:</p>

  <p>Some code in blockquote.</p>

  <p><code>javascript
  function() {
    consoel.log('hello world!');
  }
  </code></p>
</blockquote>

The correct result should be:

<blockquote>
  <p>Note:</p>

  <p>Some code in blockquote.</p>

<pre><code class="javascript language-javascript">function() {
  consoel.log('hello world!');
}</code></pre>
</blockquote>

The official demo of Showdown works well.

Marked works well, too.

So why do not use the official version of Showdown, the Ghost fork is out of date and bugly.

I really wanna know when will this issue be fixed

need fixed + 1.

row markdown:

ghost output:

When will fenced code block be supported in Ghost? Have been waiting for this for a long long time