tag:support.markedapp.com,2011-09-11:/discussions/questions/5270-githubMarked: Discussion 2018-10-19T05:38:58Ztag:support.markedapp.com,2011-09-11:Comment/320275012014-03-11T12:50:17Z2014-03-11T12:50:17ZGithub<div><p>Yes, for the most part. It uses a different processor than
GitHub does,<br>
but has accommodations for preserving line breaks, fenced code
blocks<br>
with highlighting and other features of GFM. There are some
minor<br>
differences, but for everyday README previewing it does a great
job.</p>
<p>-Brett</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/320275012014-03-11T12:53:46Z2014-03-11T12:53:47ZGithub<div><p>Thanks, Brett.</p>
<p>Larry</p></div>Larry McJunkintag:support.markedapp.com,2011-09-11:Comment/320275012015-07-09T02:44:34Z2015-07-20T21:04:06ZGithub<div><p>There's an important aberration that is hopefully easy to
fix:</p>
<p>On GitHub, a fenced code block with NO language specification
(just "~~~") results in NO syntax highlighting, while Marked 2
appears to apply highlighting nevertheless.</p></div>mklement0tag:support.markedapp.com,2011-09-11:Comment/320275012015-07-09T02:49:15Z2015-07-09T02:49:15ZGithub<div><p>If no language is specified, Marked (using highlight.js)
attempts to<br>
guess the language. You can use "nohighlight" as a language to
<em>not</em><br>
highlight specific blocks.</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/320275012015-07-09T03:06:14Z2015-07-20T21:04:06ZGithub<div><p>Thanks, Brett, that's good to know.</p>
<p>I guess I got lucky so far that highlight.js has worked as
expected for me even with NO language specified - and whatever you
use seems to guess differently.</p>
<p>However, the discrepancy is easily resolved by using
'nohighlight', which I'll do from now on.</p>
<p>Thanks for a great app.</p>
<p>Michael</p></div>mklement0