Something like a `Body` attribute that holds the original body seems
like it's within the scope of a MultiMarkdown metadata extension,
because MultiMarkdown describes both how metadata and the body are
defined.
If you think this is outside of the scope of the extension though I
totally understand. Sprawling programs are really gross.
Ian
P.S. If anyone does know about a standalone MultiMarkdown metadata
parser I'd love to hear about it!
On Thu, Jan 30, 2014 at 12:07:14AM +0000, Waylan Limberg wrote:
>I can't imagine how this would be useful. Isn't the point of the
>markdown parser to parse markdown and get html? If you want to do
>some preprocessing before passing your text into markdown, then my
>suggestion would be to do the preprocessing before passing the text
>into markdown. If that means reimplementing your own metadata
>processor, then that is probably what you should do. For instance, a
>static site generator may do this so it can allow the markup language
>of the document to be defined in the metadata. In such a situation,
>Python-Markdown's Metedata extension would not be the tool for the
>job.
>
>Waylan
>
>On 1/28/2014 7:03:37 PM, "Ian G. Jeffries" <ia...@ho...>
>wrote:
>
>>Hey folks,
>>
>>I'd like to use the 'meta' extension to get a Python string which
>>consists of the body of the post without the metadata, but
>>otherwise unchanged.
>>
>>I've got my own code to do this which works fine, but I was
>>wondering if there was a built-in option to do this that I missed.
>>If not would it be a good thing to have added?
>>
>>Cheers!
>>
>>Ian Jeffries
|
