From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: "jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
<jmuccigr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: how to generate the bibliography for a document?
Date: Fri, 20 Nov 2020 16:22:11 -0800 [thread overview]
Message-ID: <m2h7pjftjg.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <ce80a7a2-bfb3-4ff8-ac1f-26f8a0a1fa9en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
"jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <jmuccigr-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.
next prev parent reply other threads:[~2020-11-21 0:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 12:07 King John Unn
[not found] ` <89f878c1-770d-4d21-b372-15961fb5e385n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-11-18 12:28 ` AW: " denis.maier-FfwAq0itz3ofv37vnLkPlQ
2020-11-18 13:12 ` Joseph Reagle
2020-11-18 13:18 ` Gabriel Nützi
2020-11-18 13:19 ` Pranesh Prakash
[not found] ` <538a99b8-3ed4-4145-a4b7-c42145b61fefn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-11-18 19:59 ` King John Unn
[not found] ` <d3fd4aa4-cfe2-4d7f-be3d-f844dfd676aan-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-11-18 20:57 ` hex
[not found] ` <3881d8c8-1c42-d10a-ec51-c209d989579a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-11-19 0:02 ` John MacFarlane
2020-11-19 0:00 ` John MacFarlane
[not found] ` <m2a6ve5i7u.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-11-20 21:38 ` jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
[not found] ` <ce80a7a2-bfb3-4ff8-ac1f-26f8a0a1fa9en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-11-21 0:22 ` John MacFarlane [this message]
[not found] ` <m2h7pjftjg.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-11-21 14:23 ` Pranesh Prakash
[not found] ` <22933182-2014-4210-a47f-02f754995774n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-11-21 15:38 ` jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
[not found] ` <87b8a4f1-8abc-4c7a-80bf-c62408dc1b60n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-11-21 20:59 ` John MacFarlane
[not found] ` <m2blfqfmtr.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-11-21 23:20 ` jmuc...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2h7pjftjg.fsf@MacBook-Pro.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=jmuccigr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).