Opened 13 years ago

Closed 12 years ago

#337 closed enhancement (fixed)

HTML (limited) support, in addition to Markdown

Reported by: maiki interi Owned by:
Priority: trivial Milestone:
Component: programming Keywords:
Cc: Parent Tickets:


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.


Change History (6)

comment:1 by Christopher Allan Webber, 13 years ago

Component: Graphic Design / UIProgramming
Makes sense. I wonder if we want to wait for a real plugin system
before we do this?

comment:2 by maiki interi, 13 years ago

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
(` <>`_ and
` <>`_).

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

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

comment:3 by Will Kahn-Greene, 12 years ago

The original url for this bug was .
#77: related, #78: related, #120: related, #338: related

comment:4 by Jakob Kramer, 12 years ago

Type: defectenhancement

comment:5 by Jakob Kramer, 12 years ago

Would be fixed with my proposed patch in #425.

Last edited 12 years ago by Jakob Kramer (previous) (diff)

comment:6 by joar, 12 years ago

Resolution: fixed
Status: acceptedclosed

This now works.

Note: See TracTickets for help on using tickets.