Examples of all the block & escaping possibilities, with a markdown syntax and
html syntax within each.
-------
::text
indented text [#6822] <b>bold</b>
-------
~~~~
::text
fenced with tildes [#6822] <b>bold</b>
~~~~
-------
<pre>
this is pre [#6822] <b>bold</b>
</pre>
-------
<code>
this is code [#6822] <b>bold</b>
</code>
-------
<div>
this is a div [#6822] <b>bold</b>
</div>
-------
this is <pre>an inline pre [#6822] <b>bold</b> </pre> foobar
-------
this is `inline backticks [#6822] <b>bold</b>` foo
---
** [tickets:#6822] Option to bypass or escape markdown**
**Status:** open
**Created:** Thu Oct 31, 2013 08:41 PM UTC by Dave Brondsema
**Last Updated:** Thu Oct 31, 2013 08:41 PM UTC
**Owner:** nobody
All textareas take markdown input, but if you don't realize that and just type
or paste something (e.g. code sample, log file) then certain chars may convert
into markdown syntax and not render as actually intended.
A checkbox near preview & formatting help buttons could be added. (Maybe
expand to a full toolbar to help with syntax some day). Changing the data
storage for every artifact and the render calls for every artifact is a lot of
work and makes the whole system a bit more complex. If we can use markdown
syntax to escape the whole content of the entry, that could work out pretty
well I think.
Requested via [forge:feature-requests:#134] and [forge:site-support:#3470]
---
Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed
to https://sourceforge.net/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
