public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Ian Cornelius <ircornelius-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Citeproc disambiguation error (note style)
Date: Tue, 26 Jul 2022 17:32:12 -0700 (PDT)	[thread overview]
Message-ID: <8ac1d845-5ac6-4d76-8c72-d3fa9f34eed5n@googlegroups.com> (raw)


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

I find that citeproc fails to disambiguate later citations in note styles 
when the given bibliographic items are not each cited at least twice.

The attached markdown file serves to illustrate the behavior on my system. 
(Update PATH/TO/ with the path to the CSL styles repo on your system.)

Run, e.g.

$ pandoc disambiguation-test.md --citeproc -o test.html

I get the result attached as pandoc-run-1.png. Notice that the citation in 
note 2 is ambiguous.

Now uncomment the final citation in the markdown file and run pandoc again. 
If both items are cited at least twice, citeproc disambiguates properly, as 
shown in pandoc-run-2.png.

I am running pandoc 2.18.

Is this a bug, or am I missing something?

Ian Cornelius

-- 
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/8ac1d845-5ac6-4d76-8c72-d3fa9f34eed5n%40googlegroups.com.

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

[-- Attachment #2: pandoc-run-2.png --]
[-- Type: image/png, Size: 72761 bytes --]

[-- Attachment #3: disambiguation-test.md --]
[-- Type: text/markdown, Size: 1096 bytes --]

---
csl: PATH/TO/styles/modern-humanities-research-association.csl
references:
- id: Turville-PetrePuttingItRight2002
  author:
    - family: Turville-Petre
      given: Thorlac
  citation-key: Turville-PetrePuttingItRight2002
  container-title: Yearbook of Langland Studies
  issued:
    - year: 2002
  page: 41-65
  title: >-
    Putting it right: the corrections of Huntington Library MS. HM 128 and BL
    Additional MS. 35287
  title-short: Putting it right
  type: article-journal
  volume: '16'

- id: Turville-PetreSirAdrianFortescue2000
  author:
    - family: Turville-Petre
      given: Thorlac
  citation-key: Turville-PetreSirAdrianFortescue2000
  container-title: Yearbook of Langland Studies
  issued:
    - year: 2000
  page: 29-48
  title: Sir Adrian Fortescue and his copy of *Piers Plowman*
  title-short: Sir Adrian Fortescue
  type: article-journal
  volume: '14'
---

Lorem ipsum [@Turville-PetreSirAdrianFortescue2000; @Turville-PetrePuttingItRight2002].
Dolor sit [@Turville-PetrePuttingItRight2002].
<!--
Amet [@Turville-PetreSirAdrianFortescue2000].
-->

# Bibliography

[-- Attachment #4: pandoc-run-1.png --]
[-- Type: image/png, Size: 66461 bytes --]

             reply	other threads:[~2022-07-27  0:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27  0:32 Ian Cornelius [this message]
     [not found] ` <8ac1d845-5ac6-4d76-8c72-d3fa9f34eed5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-27  1:11   ` 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=8ac1d845-5ac6-4d76-8c72-d3fa9f34eed5n@googlegroups.com \
    --to=ircornelius-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).