From: Kolen Cheung <christian.kolen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: How to write a markdown source that is dual compatible with pandoc-citeproc and biblatex?
Date: Thu, 28 Apr 2016 20:29:27 -0700 (PDT) [thread overview]
Message-ID: <913c0565-345a-4a73-9c0f-3bc9f3a353c6@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1618 bytes --]
Hi,
I want to write markdown source that is dual compatible with
pandoc-citeproc and biblatex, so that in HTML output I can use
pandoc-citeproc, and in LaTeX output I can use biblatex.
There are some caveats:
<#>NoCite
If I want to use nocite, pandoc-citeproc requires
nocite: |
@abc
in the YAML front matter, but biblatex requires
\nocite{abc}
Am I missing anything?
So I need to put both for it to work. Luckily, it seems that even if I used
pandoc-citeproc in LaTeX, the extra \nocite{abc} didn’t cause error.
<#>References Heading
In pandoc-citeproc, a heading of References needed to be input manually. So
there’s no simple way to write a markdown source that is compatible with
both pandoc-citeproc (e.g. for HTML output) and biblatex (for LaTeX output).
<#>References in a List?
pandoc-citeproc seems not to put the references in a list. Is it just about
using a different citation style or something fundamental in
pandoc-citeproc?
Thanks very much in advance.
--
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/913c0565-345a-4a73-9c0f-3bc9f3a353c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 10401 bytes --]
next reply other threads:[~2016-04-29 3:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 3:29 Kolen Cheung [this message]
[not found] ` <913c0565-345a-4a73-9c0f-3bc9f3a353c6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-04-29 4:13 ` Kolen Cheung
[not found] ` <2b6130a3-e180-4886-8e42-fa4c929605d4-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-04-30 3:24 ` John MacFarlane
2016-04-30 3:22 ` John MacFarlane
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=913c0565-345a-4a73-9c0f-3bc9f3a353c6@googlegroups.com \
--to=christian.kolen-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).