From: Danh Nguyen <danhnguyen04-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Multiple bibtex files for pandoc-citeproc
Date: Mon, 12 Jan 2015 08:07:51 -0800 (PST) [thread overview]
Message-ID: <a6e78dab-ecf1-408a-bd5e-9492ea3a07fd@googlegroups.com> (raw)
In-Reply-To: <88272f03-1e43-4289-b35f-68bc803d42ae-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1312 bytes --]
Great, it works fine on the command line to specify multiple
"--bibliography" entries. Thanks for your help. Do you know of a way to do
this in the source file through YAML metadata?
- Danh
On Monday, January 12, 2015 at 10:33:20 AM UTC-5, Matthew Pickering wrote:
>
> I think on the command line you can specify --bibliography multiple times.
> Have you tried that?
>
> On Monday, January 12, 2015 at 3:27:33 PM UTC, Danh Nguyen wrote:
>>
>> Hi, can you specify multiple bib input files for pandoc-citeproc (e.g.
>> item1.bib, item2.bib, etc.), either via the pandoc command line or the
>> metadata field in the source file? I have tried multiple ways but could not
>> get the syntax right.
>>
>> Thanks and regards,
>> Danh
>>
>
--
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/a6e78dab-ecf1-408a-bd5e-9492ea3a07fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2050 bytes --]
next prev parent reply other threads:[~2015-01-12 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 15:27 Danh Nguyen
[not found] ` <3aaafb43-6204-49b2-8196-e1e8d106ad41-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-12 15:33 ` Matthew Pickering
[not found] ` <88272f03-1e43-4289-b35f-68bc803d42ae-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-12 16:01 ` Danh Nguyen
2015-01-12 16:07 ` Danh Nguyen [this message]
[not found] ` <a6e78dab-ecf1-408a-bd5e-9492ea3a07fd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-12 18:21 ` 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=a6e78dab-ecf1-408a-bd5e-9492ea3a07fd@googlegroups.com \
--to=danhnguyen04-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).