public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Joshua <joshua.kerr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Formatting of "ibid" in v2.11.x
Date: Wed, 11 Nov 2020 11:02:16 -0800 (PST)	[thread overview]
Message-ID: <557267e8-3f30-45aa-8b58-50fc6ba71531n@googlegroups.com> (raw)
In-Reply-To: <m2wnyrlqn0.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 3751 bytes --]

Thanks for such a helpful, prompt reply. I've loved pandoc for a long time, 
but I had no idea the support was this good. You have a superb project here.

After consulting the style guides, it looks like pandoc is keeping with the 
times and I am not. I'm still a bit confused about your response to the 
second issue, though. Suppose I type:
Blah.^[@AugustineCityGod2008, 72.] Blah.^[Compare to the competing claim in 
@AugustineCityGod2008, 46.]

This then renders:
[1] Augustine, *City of God*, 72.
[2] Compare to the rather different claim in Augustine, ibid, 46.

Whereas the behavior I intend:
[1] Augustine, *City of God*, 72.
[2] Compare to the rather different claim in ibid, 46.

This is the behavior I achieved before upgrading pandoc, but I do not 
understand the directives I need to give in order to achieve it now. Or 
maybe I simply cannot.

Many thanks once again,
Joshua

On Wednesday, November 11, 2020 at 10:01:25 AM UTC-8 John MacFarlane wrote:

> Joshua <joshu...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > (This is a followup to "Removing parentheses around citations in
> > footnotes": *thank you so much* for the fix there. The behavior I'm
> > noticing now is different enough that I thought it worth a separate 
> thread.)
> >
> > There seems to be an issue with "ibid." I'm using
> > chicago-note-bibliography-with-ibid.csl and a dummy file as an example.
> > Here's what I get with v2.11.1.1:
> > [1] Dodds, *Euripedes*; see also Augustine, *The City of God*.
> > [2] Augustine, *The City of God*, 72.
> > [3] Augustine, ibid, 46.
> > Note that there are two problems here: (1) it repeats the source in note 
> 2
> > instead of using "ibid",
>
> It's not clear that's a problem. Indeed, we made a change to get
> just this behavior. See
>
>
> https://github.com/jgm/citeproc/commit/5aafa0e58ce37d56677bf88f52c4e6591e867703
> https://github.com/jgm/pandoc#6813
> https://github.com/citation-style-language/documentation#121
>
> According to the spec, ibid is supposed to be triggered only when
> the cited item (a) immediately follows another cite to the same
> source within the same citation or (b) the previous citation
> "consists of a single cite referencing the same item."
>
> In this case there is some ambiguity about whether (b) is
> satisfied -- technically, it is, because the previous citation
> is just "Augustine, The City of God." However, that in-text
> citation occurs in a note with another citation, such that the
> whole thing is indistinguishable from a note citation containing
> the two items. So we treat the item as not a "single cite" in
> this case.
>
> > and (2) it repeats the author in note 3.
>
> That's because (I assume) you've used an author-in-text citation
> form, which always prints the author. Note the difference
> between
>
> blah blah [@augustine:city].
>
> and
>
> blah blah^[@augustine:city].
>
> IN the first case you have a normal citation, and the author name
> will be suppressed. In the second case, you have a footnote with
> an author-in-text citation.
>
> We need this behavior because you might say
> "@augustine:city says blah" in the main text, and we'd want
> to get "Augustine(1) says blah" with a note "(1) Ibid."
> This structure (author name + note with "ibid") gets transformed
> to "Augustine, ibid." when it is found within a note.
>
>

-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/557267e8-3f30-45aa-8b58-50fc6ba71531n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 6245 bytes --]

  parent reply	other threads:[~2020-11-11 19:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-11 16:15 Joshua
     [not found] ` <965d161d-db68-439f-acab-c035c89ec0dfn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-11-11 18:01   ` John MacFarlane
     [not found]     ` <m2wnyrlqn0.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-11-11 19:02       ` Joshua [this message]
2020-11-11 19:37         ` Denis Maier
     [not found]         ` <557267e8-3f30-45aa-8b58-50fc6ba71531n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-11-11 19:37           ` 'Denis Maier' via pandoc-discuss
2020-11-11 19:41             ` Denis Maier
     [not found]             ` <5fac3d7d.1c69fb81.8ceda.81c8SMTPIN_ADDED_MISSING-AJJneosEFeET7FrJB5NJYwC/G2K4zDHf@public.gmane.org>
2020-11-11 19:41               ` 'Denis Maier' via pandoc-discuss
     [not found]                 ` <5fac3e55.1c69fb81.f7f71.1ee3SMTPIN_ADDED_MISSING-AJJneosEFeET7FrJB5NJYwC/G2K4zDHf@public.gmane.org>
2020-11-11 19:57                   ` Joshua
2020-11-11 20:12           ` John MacFarlane
     [not found]             ` <m27dqrirf5.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-11-11 20:17               ` Joshua
2020-11-15 12:06               ` jcr
     [not found]                 ` <91253106-0a3e-4139-ab0e-2dbbed3f7been-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-11-15 16:36                   ` AW: " denis.maier-FfwAq0itz3ofv37vnLkPlQ
     [not found]                     ` <6fbe9e68e26342fda7586938e5139882-FfwAq0itz3ofv37vnLkPlQ@public.gmane.org>
2020-11-15 19:12                       ` denis.maier-FfwAq0itz3ofv37vnLkPlQ
2020-11-16 16:46                   ` John MacFarlane
     [not found]                     ` <CAGOSsdkBbvh4jYQbwK9+Ay3nWFEo_cZ0uFN=w6tDoG76hqQGYg@mail.gmail.com>
     [not found]                       ` <m2k0ul82g7.fsf@MacBook-Pro.hsd1.ca.comcast.net>
     [not found]                         ` <m2k0ul82g7.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-11-16 20:37                           ` John MacFarlane
     [not found]                             ` <m2ft5982dm.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-11-18 10:08                               ` Pandoc: Suggestions for latex table generator Gabriel Nützi
     [not found]                                 ` <277ee96f-10bd-6db4-3c2f-7ee37527d68b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-11-19 20:05                                   ` John MacFarlane
2020-11-19 20:14                                   ` John MacFarlane
     [not found]                                     ` <m2eekp3y0e.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-11-19 20:18                                       ` John MacFarlane
2020-11-22 18:13                                   ` 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=557267e8-3f30-45aa-8b58-50fc6ba71531n@googlegroups.com \
    --to=joshua.kerr-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).