From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Joseph Reagle
<joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: `-t markdown` refuses to render citations
Date: Fri, 13 Sep 2019 16:13:05 -0700 [thread overview]
Message-ID: <yh480kh85f6b9a.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <25f74181-be38-d970-46f0-d1c940dcee2c-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
-t markdown-citations
With the default +citations, the markdown citation syntax
is enabled, so you'll get @item1. With -citations, you'll
get the rendered citation.
Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> writes:
> If I have a markdown file and bib, rendering to most any output format will render the citations using the specified CSL in that format, including the markdown variants. But if I want to render to pandoc's markdown, citeproc seems to be skipped. If that's correct, is there a way to force their rendering?
>
>
> --
> 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/25f74181-be38-d970-46f0-d1c940dcee2c%40reagle.org.
--
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/yh480kh85f6b9a.fsf%40johnmacfarlane.net.
next prev parent reply other threads:[~2019-09-13 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-13 20:57 Joseph Reagle
[not found] ` <25f74181-be38-d970-46f0-d1c940dcee2c-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2019-09-13 23:13 ` John MacFarlane [this message]
[not found] ` <yh480kh85f6b9a.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-09-16 11:57 ` Joseph Reagle
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=yh480kh85f6b9a.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=joseph.2011-T1oY19WcHSwdnm+yROfE0A@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).