From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: John Carter Wood
<johannes.c.holz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Citation problems, pandoc-citeproc?
Date: Mon, 28 Oct 2019 10:57:09 -0700 [thread overview]
Message-ID: <m2tv7s69e2.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <ab2a282c-b491-4b78-86e4-526a37170e8c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
I'm not sure why it would have worked with an earlier version.
However, the documentation specifies that citations in a citation
group need to be separated by semicolons.
So [@item1; see also @item2].
That has been the documented behavior since the beginning.
John Carter Wood <johannes.c.holz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Hello,
>
> I've been using a Pandoc setup combined with Zotero and markdown
> successfully for a couple of years. But new versions of this set-up, using
> a later version of Pandoc, have been having problems: in references
> (footnotes) that use periods, subsequent reference keys are not converted
> into full references: they remain in the key format
> "@authorname_titleword_year".
>
> (The formatting of the quotation marks is correct: I'm in Germany.)
>
> Here is a sample markdown text.
>
> [image: Markdown_citation.jpg]
>
>
>
> Using this text works fine using pandoc 1.19.2.1/pandoc-citeproc 0.10.4 All
> references are converted. (The issue comes up in footnote 3.)
>
> [image: earlier_pandoc_version.jpg]
>
>
>
> However, using the *exact same* markdown text and .bib file, running pandoc
> 2.2.1/pandoc-citeproc 0.14.3.1, the second citation in footnote three does
> not convert.
>
> [image: later_pandoc_version.jpg]
>
>
> When I remove the period, it works. But I have several documents that have
> this kind of citation, and I don't want to have to go back and change them
> all. Moreover, this kind of extensive footnote with citations is normal in
> my field (history).
>
> Am I doing something wrong? or has something changed with different
> versions?
>
> I appreciate any help. And I'm happy to provide any info if I've forgotten
> something.
>
>
> --
> 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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/ab2a282c-b491-4b78-86e4-526a37170e8c%40googlegroups.com.
next prev parent reply other threads:[~2019-10-28 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-26 19:10 John Carter Wood
[not found] ` <ab2a282c-b491-4b78-86e4-526a37170e8c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-10-28 17:57 ` John MacFarlane [this message]
[not found] ` <m2tv7s69e2.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-10-28 19:36 ` John Carter Wood
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=m2tv7s69e2.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=johannes.c.holz-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).