public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Denis Maier <denis.maier.lists@mailbox.org>
To: John MacFarlane <jgm@berkeley.edu>, pandoc-discuss@googlegroups.com
Subject: Re: Numerical citations -- prefix problems
Date: Thu, 3 Sep 2020 09:44:26 +0200	[thread overview]
Message-ID: <c5ccf476-9407-fed9-8a32-da0c4f34aa82@mailbox.org> (raw)
In-Reply-To: <m2blinst0s.fsf@MacBook-Pro.hsd1.ca.comcast.net>


Ok.
Will you keep on fixing these kind of things in the light of a new 
haskell citeproc being just around the corner?

Am 03.09.2020 um 00:39 schrieb John MacFarlane:
> This is something to fix then.  A bug report on pandoc-citeproc
> could help me keep track.
>
> Denis Maier <denis.maier.lists@mailbox.org> writes:
>
>> Maybe a bug? I've tested with nature.csl
>>
>> citeproc-js in Zotero/Word gave me correct results, pandoc with
>> pandoc-citeproc didn't.
>>
>> Am 02.09.2020 um 17:44 schrieb JL:
>>> I'm trying to get prefixes to work for numerical citations (I'm using
>>> a custom CSL but have the same problem when using a standard one), but
>>> they get ignored:
>>>
>>> [cf. @cite1, p. 12] ---> [1, p. 12]
>>> [see @cite2] ---> [2]
>>>
>>> I can work around it like this
>>>
>>> [cf. [@cite1], p. 12] --> [cf. [1], p. 12]
>>>
>>> but I would like a result similar to what would author-date citations
>>> would look like
>>>
>>> [cf. 1, p. 12]
>>>
>>> Could somebody point me in the right direction? Thanks!
>>> -- 
>>> 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@googlegroups.com
>>> <mailto:pandoc-discuss+unsubscribe@googlegroups.com>.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/pandoc-discuss/a3ea9b8f-518b-4ebf-becd-7f2cad550b10n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/pandoc-discuss/a3ea9b8f-518b-4ebf-becd-7f2cad550b10n%40googlegroups.com?utm_medium=email&utm_source=footer>.
>> -- 
>> 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@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/c6259621-a343-97e1-9389-df77ed42cfea%40mailbox.org.

  reply	other threads:[~2020-09-03  7:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02 15:44 JL
     [not found] ` <a3ea9b8f-518b-4ebf-becd-7f2cad550b10n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-02 21:48   ` Denis Maier
     [not found]     ` <c6259621-a343-97e1-9389-df77ed42cfea-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2020-09-02 22:39       ` John MacFarlane
2020-09-03  7:44         ` Denis Maier [this message]
     [not found]           ` <c5ccf476-9407-fed9-8a32-da0c4f34aa82-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2020-09-03 16:32             ` 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=c5ccf476-9407-fed9-8a32-da0c4f34aa82@mailbox.org \
    --to=denis.maier.lists@mailbox.org \
    --cc=jgm@berkeley.edu \
    --cc=pandoc-discuss@googlegroups.com \
    /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).