From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Joost Kremers
<joostkremers-97jfqw80gc6171pxa8y+qA@public.gmane.org>,
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Cc: jiewuza <jiewuza-9Onoh4P/yGk@public.gmane.org>
Subject: Re: Could --biblatex use autocite instead of autocites so as to support numeric-comp style?
Date: Fri, 12 Oct 2018 09:28:04 -0700 [thread overview]
Message-ID: <yh480klg73xh7v.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <87zhvk5wby.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
If I followed this thread, I thought the gist of it
was that OP had seen, experimentally, that
\autocites{a}{b}{c} gives different output than
\autocite{a,b,c}.
Joost Kremers <joostkremers-97jfqw80gc6171pxa8y+qA@public.gmane.org> writes:
> On Mon, Oct 08 2018, John MacFarlane wrote:
>> I'm not an expert on biblatex, but the idea of using
>> \autocite{a,b,c} instead of \autocites{a}{b}{c} when
>> there are no prefixes, suffixes, or locators seems
>> good to me.
>>
>> Does anyone see a problem with this?
>
> Well, the biblatex manual says that "[t]he multicite commands
> are built on top of backend commands like \parencite and
> \footcite". That suggests to me that \autocites{a}{b}{c} is
> actually equavalent to \autocite{a,b,c}, so it shouldn't be a
> problem.
>
> --
> Joost Kremers
> Life has its moments
>
> --
> 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/87zhvk5wby.fsf%40fastmail.fm.
> For more options, visit https://groups.google.com/d/optout.
prev parent reply other threads:[~2018-10-12 16:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 1:59 jiewuza
[not found] ` <m2h8i19mrt.fsf-9Onoh4P/yGk@public.gmane.org>
2018-10-05 2:40 ` John MacFarlane
2018-10-05 5:35 ` jiewuza
[not found] ` <m2d0sp9crm.fsf-9Onoh4P/yGk@public.gmane.org>
2018-10-05 17:01 ` John MacFarlane
2018-10-06 13:28 ` jiewuza
2018-10-06 13:37 ` jiewuza
[not found] ` <m24ldz9owk.fsf-9Onoh4P/yGk@public.gmane.org>
2018-10-07 17:57 ` John MacFarlane
2018-10-08 2:08 ` jiewuza
2018-10-08 2:33 ` jiewuza
[not found] ` <m2va6d88wl.fsf-9Onoh4P/yGk@public.gmane.org>
2018-10-08 17:07 ` John MacFarlane
2018-10-09 2:35 ` jiewuza
[not found] ` <yh480kwoqsfju9.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2018-10-11 15:36 ` Joost Kremers
[not found] ` <87zhvk5wby.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2018-10-12 16:28 ` John MacFarlane [this message]
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=yh480klg73xh7v.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=jiewuza-9Onoh4P/yGk@public.gmane.org \
--cc=joostkremers-97jfqw80gc6171pxa8y+qA@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).