public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: jiewuza <jiewuza-9Onoh4P/yGk@public.gmane.org>,
	pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Could --biblatex use autocite instead of autocites so as to support numeric-comp style?
Date: Mon, 08 Oct 2018 10:07:26 -0700	[thread overview]
Message-ID: <yh480kwoqsfju9.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <m2va6d88wl.fsf-9Onoh4P/yGk@public.gmane.org>


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?

I suggest you put an issue on pandoc's bug tracker
so this won't be forgotten.

jiewuza <jiewuza-9Onoh4P/yGk@public.gmane.org> writes:

> Also I was rethinking what you have proposed:
>
> ```
> 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?
> ```
>
> I think it should.
> Even such a macro can be defined, it does not work
> when there are prefix, suffix, and locator.
>
> While on the other hand, it is common that there
> are no prefix, suffix, or locator, and autocite is preferred.
>
>
> John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> writes:
>
>> jiewuza <jiewuza-9Onoh4P/yGk@public.gmane.org> writes:
>>
>>> What I have tried is
>>>
>>> I config autocite=superscript for biblatex
>>> ```
>>>  \usepackage[sorting=none, style=numeric-comp,
>>>    autocite=superscript]{biblatex}
>>> ```
>>> This will make autocite work as supercite, according to biblatx document.
>>
>> My suggestion was to redefine \autocites (perhaps in
>> addition to \autocite).
>>
>> If you can define a macro that rewrites
>>
>> \autocites{a}{b}{c}
>>
>> to
>>
>> \autocite{a,b,c}
>>
>> then you'll be there, right?  If you need help with
>> that, the tex stack exchange is probably a better
>> place than here.
>
> -- 
> 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/m2va6d88wl.fsf%40163.com.
> For more options, visit https://groups.google.com/d/optout.


  parent reply	other threads:[~2018-10-08 17:07 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 [this message]
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=yh480kwoqsfju9.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=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).