I'd tried that, but code spans in the metadata appear to cause the json writer to bail. I thought they weren't supported. For example, if I run `pandoc -t json` on this:

---
foo: `bar`
...

I get this:

pandoc: Could not parse YAML header: found character that cannot start any token "source" (line 3, column 6)
[{"unMeta":{}},[]]

Am I doing it wrong? I am using pandoc 1.13.2.1.

On Friday, May 15, 2015 at 4:54:54 AM UTC+1, John MacFarlane wrote:
If you're using filters, then one option would be to use a code span
for your literal text:

    my_field: `eek*ook*`

The filter could then intercept these fields and convert these to
"String" metadata fields.  Or maybe you wouldn't need to convert them,
depending on your purposes.

--
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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/3941739e-8de2-46d9-9bc0-319c31631e3e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.