When using CSL-JSON, the input format needs to be specified explicitly:
```
$ pandoc -f csljson mybib.json -s -o formatted-bibliography.html
```
It won't work without the `-f csljson`. It will still work without that flag when the bibliography input format is CSL-YAML or BibLaTeX though, since the former is read as Markdown and the latter's format is guessed using its extension (.bib).
I hope that helps.
As a side note, perhaps including a more descriptive warning/error message might be helpful. For .y{a}ml input files, the warning says:
[WARNING] Could not deduce format from file extension .y{a}ml
Defaulting to markdown
Regards,
Pranesh
On Saturday, 21 November, 2020 at 5:52:30 am UTC+5:30 John MacFarlane wrote:
"jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> This isn't working for me with json input (from Zotero). bib (also from
> Zotero) works just fine. I'm getting this error with the json:
>
> ```JSON parse error: Error in $: mempty```
>
> even with a json file with only one entry that json_verify is happy with.
> The pandoc command is barfing on it. The old, nocite way works fine still.
Post it here; maybe it's a bug?
> PS A side note: the new method with --citeproc generates html spans every
> place the bib has double curly brackets to preserve cases in title. Seems
> unnecessary.
True, but also pretty harmless. We could get rid of them but
there might be some performance penalty.
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/22933182-2014-4210-a47f-02f754995774n%40googlegroups.com.