HTML (limited) support, in addition to Markdown

[maiki interi]

I see from `#362 </issues/362>`_, `#363 </issues/363>`_ and
`#410 </issues/410>`_ that a lot of effort was put into Markdown
support. And `#379 </issues/379>`_ demonstrates that the fields
have to be scrubbed anyhow. So, I am wondering if it is possible
allow/configure HTML in all the applicable fields.

Without getting into it, I use HTML, Textile and Markdown (and
various wiki syntaxes) habitually, but hardly anyone else I know
does. All my cool friends know how to create an anchor element in
HTML, though.

Of course white-listing elements is probably useful. I imagine that
this could be configured with overrides, but it is fairly simple to
find a reasonable default set of elements to allow.

Thoughts?

[Christopher Allan Webber]

Makes sense. I wonder if we want to wait for a real plugin system
before we do this?

[maiki interi]

Christopher Webber wrote:

    Makes sense. I wonder if we want to wait for a real plugin system
    before we do this?


I think that would great. I presume that mg will have a default set
of plugins that contain features that not everyone will use, but a
lot of people will. One that provides multi-tiered (to be able to
use multiple syntaxes at once, in a specific order) text filtering
would be awesome.

The common filters I use for websites are full and limited *HTML*,
*Markdown* and *Textile*. So-called "limited" HTML filters normally
have a couple of useful presets, like line-breaks become new
paragraphs, and certain patterns become links
(`http://example.org <http://example.org>`_ and
`mail@addresses.com <mailto:mail@addresses.com>`_).

If the plugin loaded arbitrary filter sets, we could do some fun
shortcodes, like ``[[t:Awesome Pics]]`` going to
``/tag/awesome-pics``.

Okay, I will keep this issue in mind for when we get to plugins.
=]

[Will Kahn-Greene]

The original url for this bug was ​http://bugs.foocorp.net/issues/689 .
Relations:
#77: related, #78: related, #120: related, #338: related

[Jakob Kramer]

Would be fixed with my proposed patch in #216.

[joar]

This now works.