HI Ian.
Thanks for the pointer.
It's an interesting approach though, if I did understand it, that
requeries the "raw" markup source's name to be hardcoded into the
middleware, right (e.g. 'description')?
If so, I am back to square one, for among all models I have quite a few
that must be parsed
Hi Arthur.
I do something similar to this.
I chose to implement it in middleware
http://svn.zyons.python-hosting.com/trunk/zilbo/common/text/
middleware/Markup.py
in a nutshell, if the 'description' field exists it will create the
description_html field in the post, which would get applied
In a current project, I've got a lot of fields that must accept markup.
Currently I am using markdown to parse the raw text. I am aware of the
useful template tags to apply markdown on the template itself, but
since reads are much more common than writes I would like to store the
markup on the
3 matches
Mail list logo
