From: Jonathan Reeve <jon.reeve-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Is it possible to convert markdown to markdown, but expand citations using pandoc-citeproc?
Date: Sun, 10 May 2015 17:18:22 -0700 (PDT) [thread overview]
Message-ID: <acdb6a15-ff68-45f1-a01c-4facc12a6b91@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 948 bytes --]
I've been trying to convert a markdown file to another markdown file, but
expand citations using pandoc-citeproc. I tried the command:
pandoc -o rmwm-chapter-compiled2.md rmwm-chapter.md --filter pandoc-citeproc
But citations are still there in the uncompiled format, i.e. [@Milesi1972
3]. Is there a way to get the filter to work when converting markdown to
markdown?
--
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/acdb6a15-ff68-45f1-a01c-4facc12a6b91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 1373 bytes --]
next reply other threads:[~2015-05-11 0:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 0:18 Jonathan Reeve [this message]
[not found] ` <acdb6a15-ff68-45f1-a01c-4facc12a6b91-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-05-11 3:22 ` John MacFarlane
[not found] ` <20150511032252.GA19916-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>
2020-03-13 16:36 ` Arjun Krishnan
[not found] ` <a67b666b-fb17-432e-893a-ef51a67e0797-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-03-13 21:28 ` John MacFarlane
[not found] ` <yh480ktv2sosg9.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-03-14 1:01 ` Arjun Krishnan
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=acdb6a15-ff68-45f1-a01c-4facc12a6b91@googlegroups.com \
--to=jon.reeve-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).