public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: jiewuza <jiewuza-9Onoh4P/yGk@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Could --biblatex use autocite instead of autocites so as to support numeric-comp style?
Date: Sat, 06 Oct 2018 21:28:40 +0800	[thread overview]
Message-ID: <m28t3b9pbr.fsf@163.com> (raw)
In-Reply-To: <m2mursba5b.fsf@johnmacfarlane.net>


But after all my efforts, I still cannot make autocites work as I want.


John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> writes:

> I'm reluctant to make that kind of change in the
> defaults.  But you can always create a custom template
> that imports biblatex with this option and redefines
> \autocites in a way that makes it behave like you want.
>
> jiewuza <jiewuza-9Onoh4P/yGk@public.gmane.org> writes:
>
>> Or is it possible to make autocites support numeric-comp?
>> So that we can get all the benefits.
>>
>> I found something at
>> https://tex.stackexchange.com/questions/114987/biblatex-supercite-with-square-brackets-and-grouped
>> but it is for supercite. 
>>
>> John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> writes:
>>
>>> I believe we use autocites because in principle each
>>> of the citations could have prefix, suffix, and
>>> locator, and this would be impossible to represent
>>> with autocite. Of course, in the case where there
>>> are no prefix, suffix, or locator, autocite could
>>> be used instead, and maybe it should.  Does anyone
>>> have opinions on this?
>>
>> -- 
>> 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/m2d0sp9crm.fsf%40163.com.
>> For more options, visit https://groups.google.com/d/optout.


  reply	other threads:[~2018-10-06 13: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 [this message]
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

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=m28t3b9pbr.fsf@163.com \
    --to=jiewuza-9onoh4p/ygk@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).