tag:support.markedapp.com,2011-09-11:/discussions/questions/6643-including-unprocessed-text-with-linking-to-a-fileMarked: Discussion 2016-08-11T03:16:46Ztag:support.markedapp.com,2011-09-11:Comment/347867672014-09-30T17:51:43Z2014-09-30T17:51:44ZIncluding unprocessed text with linking to a file<div><p>Ooops.. Title should have read "without linking to a file".
Sigh.</p></div>Michael Morrisontag:support.markedapp.com,2011-09-11:Comment/347867672014-09-30T18:44:44Z2014-09-30T18:44:44ZIncluding unprocessed text with linking to a file<div><p>Not by default. You could have a simple custom processor that
replaced<br>
them with placeholders, ran a markdown processor, and then
replaced<br>
them.</p>
<p>If you're outputting to HTML and pasting that to your blog, you
can<br>
always escape the first square bracket ([shortcode]), which should
keep<br>
a Markdown processor from doing anything to it and the slash
wouldn't<br>
show up in the export. It would be wrapped in</p>
<p>tags, though.</p>
<p>-Brett</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/347867672014-09-30T19:36:20Z2014-09-30T19:36:22ZIncluding unprocessed text with linking to a file<div><p>Hello Brett,</p>
<p>Thanks for your quick reply!</p>
<p>I tried the backslash, and find that WP is still choking on the
converted characters. So,</p>
<p><code>[caption id="attachment_314"
align="aligncenter"</code></p>
<p>is converted to</p>
<p><code>[caption id=&#8220;attachment_314&#8221;
align=&#8220;aligncenter&#8221;</code></p>
<p>And WP becomes confused. So it looks like I need to send the
whole section of text, unprocessed, and not just suppress the first
"[". Yes, it does wrap in</p>
<p>tags, but this doesn't seem to be the problem...</p>
<p>If you have further thoughts, I look forward to hearing
them!</p>
<p>Many thanks,</p>
<p>Michael</p></div>Michael Morrisontag:support.markedapp.com,2011-09-11:Comment/347867672014-09-30T20:30:58Z2014-09-30T20:30:58ZIncluding unprocessed text with linking to a file<div><p>What I recommend is putting this plugin on your wordpress blog
and just<br>
posting the Markdown itself after previewing:<br>
<a href=
"https://wordpress.org/plugins/markdown-on-save-improved/">https://wordpress.org/plugins/markdown-on-save-improved/</a></p>
<p>It saves the HTML and the Markdown at the same time, so you can
edit<br>
your post in MD and still not have to render it on the front end
for<br>
every page load.</p>
<p>-Brett</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/347867672014-09-30T22:39:35Z2014-09-30T22:39:39ZIncluding unprocessed text with linking to a file<div><p>Thanks Brett!</p>
<p>I'll see what I can do!</p>
<p>Does it make sense to have such a capability? A syntax that
says, "don't render this text, but stick it in just like it
is"?</p>
<p>Thanks so much for Marked, which I use every day!</p>
<p>Michael</p></div>Michael Morrisontag:support.markedapp.com,2011-09-11:Comment/347867672014-09-30T23:19:34Z2014-09-30T23:19:34ZIncluding unprocessed text with linking to a file<div><p>You can use divs to do it. I didn't think about that. Use:</p>
<div>[shortcode]</div>
<p>If you turn off "Process Markdown inside of HTML" in the
Processor<br>
preferences, it won't even wrap the p tags. It's an extra div in
the<br>
markup output, but it won't be visible on the front end.</p></div>Brett