At Wed, 12 Feb 2014 14:02:12 +0100, Nicolas Goaziou wrote: > > Hello, > > Erik Hetzner <e...@e6h.org> writes: > > > I have been looking at publishing to HTML using pandoc. Because pandoc > > requires post-processing to transform the org-mode markdown output to > > other formats, it is necessary to use the post-process parameter of > > org-export-to-file. > > > I think this patch makes sense; let me know what you think. > > Thanks for your patch. > > Though, it is not necessary. `post-process' is meant for processing > after an asynchronous export (e.g., prepare a buffer in the current > process). > > You're looking after a filter. See > > (info "(org) Advanced configuration") > > for more information.
Hi Nicholas, Thanks very much for your response (and ox.el)! I looked at filters, but concluded they were not appropriate, because pandoc operates on the file as a whole, and writes to a file, and can return binary content (for example, if it is generating PDFs). It seemed equivalent to the way that the latex exporter uses pdflatex to generate a PDF, and the latex exported uses a post-process function. I could be wrong, though. It would also be convenient to have access to the info plist; in fact, I was going to write another email about having access to the info plist in a post-process filter. Is there a way to define a filter that operates on the entire content, is guaranteed to run after everything else, and can handle binary content? Thanks. best, Erik -- Sent from my free software system <http://fsf.org/>.
