public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Gu Lu <guill.louvel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Converting Markdown to (Multi)Markdown but citations are getting expanded twice?
Date: Tue, 5 May 2020 07:09:28 -0700 (PDT)	[thread overview]
Message-ID: <261c27ed-275a-4b07-9eab-d6b584bec482@googlegroups.com> (raw)
In-Reply-To: <5041cd75-7c55-41ec-a8c6-ac28580a39ef-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2864 bytes --]

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.

Le mardi 5 mai 2020 13:40:31 UTC+2, Balaji a écrit :
>
> Hello,
>
> I'm very new to using tools such as pandoc so it's very possible that this 
> is a case of mis-reading TFM, but hours of searching thru Stackoverflow and 
> other community posts have left me at a dead-end so I hope someone can help 
> me out.
>
> I'm trying to convert Markdown files that have BiBTeX style citations into 
> Markdown again but expand the citation as a footnote. I've come close using 
> the Chicago Manual of Style 17th edition CSL but am finding that the 
> citation gets expanded twice. A minimal example below:
>
> Original Markdown file - cite.md:
> Here is one reference citing the Reactome Project. [^1]
>
> [^1]: @deustachio_2003
>
>
> BiB file - cite.bib:
> @article{deustachio_2003, title={Pentose phosphate pathway}, volume={5}, 
> DOI={10.3180/react_1859.1}, journal={Reactome - a curated knowledgebase 
> of biological pathways}, author={Deustachio, P}, year={2003}, month={Mar}}
>
> Pandoc command:
> pandoc cite.md --filter pandoc-citeproc -t markdown_mmd -o cite-new.md --
> bibliography=cite.bib --csl=chicago-full.csl
>
> Output file - cite-new.md:
> Here is one reference citing the Reactome Project.[^1]
>
> <div id="refs" class="references hanging-indent" markdown="1">
>
> <div id="ref-deustachio_2003" markdown="1">
>
> Deustachio, P. “Pentose Phosphate Pathway.” *Reactome - a Curated
> Knowledgebase of Biological Pathways* 5 (March 2003).
> <https://doi.org/10.3180/react_1859.1>.
>
> </div>
>
> </div>
>
> [^1]: P Deustachio, “Pentose Phosphate Pathway,” *Reactome - a Curated
>     Knowledgebase of Biological Pathways* 5 (March 2003),
>     <https://doi.org/10.3180/react_1859.1>
>
> I have not been able to figure out how to prevent the additional citation 
> in the <div></div> from appearing in the output Markdown file and would 
> appreciate any help in this regard!
>
> FWIW, this is using pandoc 2.9.2.1 on Windows.
>

-- 
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/261c27ed-275a-4b07-9eab-d6b584bec482%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 12135 bytes --]

  parent reply	other threads:[~2020-05-05 14:09 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 [this message]
     [not found]     ` <261c27ed-275a-4b07-9eab-d6b584bec482-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-05-06  1:11       ` Balaji Dutt

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=261c27ed-275a-4b07-9eab-d6b584bec482@googlegroups.com \
    --to=guill.louvel-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).