Is that a realistic scenario?

At least in my case of pantable it actually is. Because either way it is 
calling pandoc to do some heavy lifting. So many of the functions I wrote 
will be the same. The only differences are how the options are given, and 
then how the input/output format might be different (e.g. from csv as a 
filter expects the csv in CodeBlock, but from csv on cli expects just a 
plain csv).

As for hierarchical metadata structures being ugly I don’t think they are.

They aren’t if in YAML, but they seems to be when specified using -M (or am 
I missing something?). In the case of any of the suggested method, the 
filter arg is only available to that particular filter, so there’s no 
mixing of name spaces. And just to add that sometimes it is not desirable 
to put this info in the YAML. e.g. when converting all pandoc Table to 
other formats (currently I only have CSV in CodeBlock output, but I might 
add some others soon, and not to mention it can works the other way 
around), one want to be able to input any random sources (it would very 
well be from a .docx) and have the ability to specifies the output format 
(say CSV in ClodeBlock, CSS tables using Div, etc.) *without* touching the 
documents.
​

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/de2e97b1-17a4-4f70-8c17-b3cd960dceb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.