Converting a Para element to BlockQuote about panflute HOT 5 CLOSED

Hi Nick,

The way I tackled this issue was by taking advantage of "yaml blocks" (api) and using them for other purposes. For instance, this is the example filter:

#!/usr/bin/env python3

"""
Converts poetics
"""

import io
import csv
import panflute as pf

def fenced_action(options, data, element, doc):
    para = pf.convert_text(element.text)
    block = pf.BlockQuote(*para)
    return block

def main(doc=None):
    return pf.run_filter(pf.yaml_filter,
                         tag='poem',
                         function=fenced_action,
                         doc=doc)

if __name__ == '__main__':
    main()

And this is the example markdown file:

This is just some normal text that is prose. It might have some _markdown_.

~~~ poem
this is a
line of a poem

and this is yet _another_
stanza of a poem that has a really long line which will wrap
and more **markdown** in it
~~~

And then this is some **more** markdown that follows.

Basically, it's quite tricky to match brackets (such as |||: and |||) so I just gave up and resorted to this approach. If you really want to use the three pipes, you can also replace the pipes into tildes right before calling pandoc/panflute.

Cheers,
S

from panflute.

Thanks @sergiocorreia, this is working well! I've updated to using a codeblock syntax as you've suggested since it is more standard across markdown.

Given a case like this:

```poem style='italic'
And in a blink, we rise above the tarmac
and the city shrinks. The problems there
seem miniscule instantly compared to the
grandeur of the world around. You transform
in moments from the ants milling about into
the birds soaring above.
```

where there is some sort of option passed to the codeblock (as supported in superfences, is there anyway to ignore this text for processing it? When I have a block like above and try to process it with your code to latex, it seems to get confused and process it as a normal paragraph rather than the "poem".

from panflute.

To clarify, I don't intend to use the style='italic' string for any use within pandoc, it can simply be ignored.

from panflute.

The code snipped used yaml blocks (~~~) instead of code blocks (what superfences use), but you can just adapt the underlying code in yaml_filter() for the other type of blocks. The extra options should be ignored automatically then.

from panflute.

Got it. Thanks for all of your help!

from panflute.