From: Balaji Dutt <balaji.dutt-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Converting Markdown to (Multi)Markdown but citations are getting expanded twice?
Date: Wed, 6 May 2020 09:11:59 +0800 [thread overview]
Message-ID: <CAF3DyWmMRKDw5MncGpekcXbtozwTT7f0QGacmW_M4aygB1=YvA@mail.gmail.com> (raw)
In-Reply-To: <261c27ed-275a-4b07-9eab-d6b584bec482-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]
On Tue, May 5, 2020 at 10:09 PM Gu Lu <guill.louvel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> This is because you are mixing footnotes and citations. *@deustachio_2003*
> is a text citation: it will be expanded into e.g. "(Deustachio 2003)" or
> "[1]" depending on your citation style. It is equivalent to the latex
> *\cite{deustachio_2003}* command. This is not to be confused with items
> in the bibliography. The bibliography will automatically be created at the
> end of the document, so no need to make it yourself using footnotes.
>
Thanks for the hint Gu. Some further searching turned up the
suppress-bibliography option in pandoc so running the same command as
before but with an additional parameter of --metadata=suppress-bibliography
got me the output I was looking for:
Here is one reference citing the Reactome Project.[^1]
[^1]: P Deustachio, “Pentose Phosphate Pathway,” *Reactome - a Curated
Knowledgebase of Biological Pathways* 5 (March 2003),
<https://doi.org/10.3180/react_1859.1>
--
Balaji
--
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/CAF3DyWmMRKDw5MncGpekcXbtozwTT7f0QGacmW_M4aygB1%3DYvA%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 4984 bytes --]
prev parent reply other threads:[~2020-05-06 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 11:40 Balaji
[not found] ` <5041cd75-7c55-41ec-a8c6-ac28580a39ef-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-05-05 14:09 ` Gu Lu
[not found] ` <261c27ed-275a-4b07-9eab-d6b584bec482-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-05-06 1:11 ` Balaji Dutt [this message]
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='CAF3DyWmMRKDw5MncGpekcXbtozwTT7f0QGacmW_M4aygB1=YvA@mail.gmail.com' \
--to=balaji.dutt-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).