Comments (16)
With the new code in citeproc branch, I get (plain text output):
Test.[1]
Test.[2]
Test.[3]
Doe, John. “Test,” n.d.
[1] Doe, “Test,” 12.
[2] asdfasdf
[3] Doe, “Test,” 12.
so this seems to be working. But there are still some bugs to iron out.
from citeproc.
You definitely don't want "ibid" in note 14, as people might think it's a reference to Doe 2006, and would have no way of knowing it's to 2005. So I'm glad pandoc can now achieve that. Note also the ibid within note 13, referring to an earlier citation in the same note. That also is correct, I believe.
from citeproc.
Are you saying it should be subsequent because of the intervening footnote?
That's still something I need to figure out. Currently citeproc only knows about the citations passed in to it, not about other, non-citation notes. I think that's fixable but so far I haven't done it. You can leave this here.
from citeproc.
I've started to add code to help with this, but looking at the spec, it doesn't say anything about this; it generally talks of distance between citations rather than between notes, and ignores the possibility of notes that occur between citations.
from citeproc.
I've started to add code to help with this, but looking at the spec, it doesn't say anything about this; it generally talks of distance between citations rather than between notes, and ignores the possibility of notes that occur between citations.
I'll discuss whether we should add this to the spec.
from citeproc.
Here's another nice test:
---
csl: ../styles/bioethics.csl
references:
- id: test
title: Test
author:
family: Doe
given: John
---
Irrelevant.^[note]
Test [@test, 12].
Test.^[asdfasdf]
Test [@test, 12].
I currently get:
Irrelevant.[1]
Test.[2]
Test.[3]
Test.[4]
[1] note
[2] J. Doe. Test: 12.
[3] asdfasdf
[4] Doe (cited n. 2) : 12.
which looks right. Deleting the asdf note gives you Ibid for the final citation, also right.
Only problem I'm still having is a spurious Ibid. in the current test/command/citeproc-chicago-fullnote-citation.md
test.
What's happening there is that citeproc thinks that the last citation to Doe 2005 is a citation with just one item. Well, it is, technically. But this citation occurs in a pandoc footnote with two citations, so probably we don't want an Ibid.
from citeproc.
What's happening there is that citeproc thinks that the last citation to Doe 2005 is a citation with just one item. Well, it is, technically. But this citation occurs in a pandoc footnote with two citations, so probably we don't want an Ibid.
Good question what the most reasonable behaviour would be. Different users might want different results...
Maybe a ibid-strictness
option could help here... either in CSL or just as a pandoc option. I'll check what citeproc-js does in these cases.
The general issue aside: a mancite command could be used to deal with these edge cases.
from citeproc.
I think for now I'll keep the current behavior.
I think I have it working well now.
from citeproc.
I think this is all working now.
Tests added to pandoc.
from citeproc.
Great. I'll test with the latest dev version.
Ok: Did a first test. Seems to work so far. Thank you!
from citeproc.
Only problem I'm still having is a spurious Ibid. in the current
test/command/citeproc-chicago-fullnote-citation.md
test.What's happening there is that citeproc thinks that the last citation to Doe 2005 is a citation with just one item. Well, it is, technically. But this citation occurs in a pandoc footnote with two citations, so probably we don't want an Ibid.
I couldn't find the test.
Anyway... citeproc-js also produces ibids. if there are two citations in one footnote. I'll open an issue over at the csl schema repo issue tracker to discuss this.
from citeproc.
I've got pandoc working now for this.
It doesn't produce the ibids in the case mentioned.
The test is in pandoc, by the way.
```
% pandoc -t markdown-citations
---
bibliography: command/biblio.bib
csl: 'command/chicago-fullnote-bibliography.csl'
link-citations: true
---
Pandoc with citeproc-hs
=======================
[@nonexistent]
@nonexistent
@item1 says blah.
@item1 [p. 30] says blah.
@item1 [p. 30, with suffix] says blah.
@item1 [-@item2 p. 30; see also @пункт3] says blah.
In a note.[^1]
A citation group [see @item1 chap. 3; also @пункт3 p. 34-35].
Another one [see @item1 p. 34-35].
And another one in a note.[^2]
Citation with a suffix and locator [@item1 pp. 33, 35-37, and nowhere
else].
Citation with suffix only [@item1 and nowhere else].
Now some modifiers.[^3]
With some markup [*see* @item1 p. **32**].
References {#references .unnumbered}
==========
[^1]: @пункт3 [p. 12] and a citation without locators [@пункт3].
[^2]: Some citations [see @item1 chap. 3; @пункт3; @item2].
[^3]: Like a citation without author: [-@item1], and again
[-@item1], and now Doe with a locator [-@item2 p. 44].
^D
[WARNING] Citeproc: citation nonexistent not found
Pandoc with citeproc-hs
=======================
[^1]
[^2]
[Doe](#ref-item1)[^3] says blah.
[Doe](#ref-item1)[^4] says blah.
[Doe](#ref-item1)[^5] says blah.
[Doe](#ref-item1)[^6] says blah.
In a note.[^7]
A citation group.[^8]
Another one.[^9]
And another one in a note.[^10]
Citation with a suffix and locator.[^11]
Citation with suffix only.[^12]
Now some modifiers.[^13]
With some markup.[^14]
References {#references .unnumbered}
==========
::: {#refs .references .hanging-indent}
::: {#ref-item2}
Doe, John. "Article." *Journal of Generic Studies* 6 (2006): 33--34.
:::
::: {#ref-item1}
---------. *First Book*. Cambridge: Cambridge University Press, 2005.
:::
::: {#ref-пункт3}
Doe, John, and Jenny Roe. "Why Water Is Wet." In *Third Book*, edited by
Sam Smith. Oxford: Oxford University Press, 2007.
:::
:::
[^1]: [**Nonexistent?**](#ref-nonexistent)
[^2]: [**Nonexistent?**](#ref-nonexistent)
[^3]: [2005](#ref-item1).
[^4]: [Ibid., 30](#ref-item1).
[^5]: [Ibid.](#ref-item1), with suffix.
[^6]: [2005](#ref-item1); [2006, 30](#ref-item2); see also [Doe and
Roe](#ref-пункт3).
[^7]: [Doe and Roe](#ref-пункт3) ([12](#ref-пункт3)) and a citation
without locators ([Doe and Roe](#ref-пункт3)).
[^8]: See [Doe, 2005, chap. 3](#ref-item1); also [Doe and Roe,
34--35](#ref-пункт3).
[^9]: See [Doe, 2005, 34--35](#ref-item1).
[^10]: Some citations (See [ibid., chap. 3](#ref-item1); [Doe and
Roe](#ref-пункт3); [Doe, 2006](#ref-item2)).
[^11]: [Doe, 2005, 33, 35--37](#ref-item1), and nowhere else.
[^12]: [Doe, 2005](#ref-item1) and nowhere else.
[^13]: Like a citation without author: ([Ibid.](#ref-item1)), and again
([Ibid.](#ref-item1)), and now Doe with a locator ([2006,
44](#ref-item2)).
[^14]: *See* [Doe, 2005, 32](#ref-item1).
```
from citeproc.
You definitely don't want "ibid" in note 14, as people might think it's a reference to Doe 2006, and would have no way of knowing it's to 2005. So I'm glad pandoc can now achieve that. Note also the ibid within note 13, referring to an earlier citation in the same note. That also is correct, I believe.
That looks good to me. I also think this is how it should be.
Just two questions regarding note 13 and 14:
- Why is the markup around the locator not in the expected result? Shouldn't it be:
[^14]: *See* [Doe, 2005, **32**](#ref-item1).
?
Then: If we change the location of the citations:
Text.[^1]
A citation [see @item1 p. 32].
[^1]: Like a citation without author: [-@item2], and again
[-@item1], and now Doe with a locator [-@item1 p. 44].
In this case, what is the result? Should there an "ibid." in the second footnote?
from citeproc.
Why is the markup around the locator not in the expected result?
parseLocator
takes the raw suffix and parses it into a locator label, locator text, and the rest.
The locator text is just plain text (and needs to be for stuff like ranges), so we ignore formatting.
There might be a better way, but this seems a rare case anyway.
In this case, what is the result? Should there an "ibid." in the second footnote?
You get this:
Text.[1]
A citation.[2]
Doe, John. “Article.” Journal of Generic Studies 6 (2006): 33–34.
———. First Book. Cambridge: Cambridge University Press, 2005.
[1] Like a citation without author: (“Article,” Journal of Generic
Studies 6 (2006): 33–34), and again (First Book (Cambridge: Cambridge
University Press, 2005)), and now Doe with a locator (Ibid., 44).
[2] See ibid., 32.
I think that's correct too. (Though here one might raise questions.)
By the way, there's something a bit off about capitalization -- Ibid. is sometimes capitalized, sometimes not; I'm having trouble figuring out what rules citeproc-js uses for this kind of thing, just going by the test suite. They don't seem to be documented.
from citeproc.
Also, the doubled parens in n. 1 are awkward. That's a result of converting a note citation that occurs within a note into a parenthetical. Maybe it would be better to use square brackets? This is a style people should try to avoid, anyway.
from citeproc.
I think that's correct too. (Though here one might raise questions.)
Correct, yes. But, I remember seeing instructions like: Avoid ibids if they don't refer to a citation only note. (That's why I contemplated having a ibid-strictness
setting, or so. But that's perhaps something for later.)
By the way, there's something a bit off about capitalization -- Ibid. is sometimes capitalized, sometimes not; I'm having trouble figuring out what rules citeproc-js uses for this kind of thing, just going by the test suite. They don't seem to be documented.
Hmm, I think it should be capitalized at the beginning of a note or at the beginning of a sentence.
Also, the doubled parens in n. 1 are awkward. That's a result of converting a note citation that occurs within a note into a parenthetical. Maybe it would be better to use square brackets?
At least Chicago require this kind of parentheses-to-brackets-conversion for parentheses inside parentheses. Should work very much like quotation marks inside quotaiton marks. But I've heard it's a language specific thing. While that is common in US English (and German), British English does not seem to require such a conversion.
Just an idea: As this is more general typographic question: Maybe this could be dealt with in Pandoc proper?
from citeproc.
Related Issues (20)
- disambiguation error (note style)
- Detection of English-language entries only permits ISO 639-1 codes HOT 2
- Reference stripped from the output in cites with position "ibid" and a suffix without a locator HOT 7
- How could citeproc support CSL-M layout? HOT 40
- `link-bibliography` option does not hyperlink references without URLs in notes HOT 6
- Localizing parts of citations HOT 5
- Error in latex generation of portuguese quotes in CSLReferences field HOT 15
- Installing the executable HOT 2
- [Help] Author only citations BibTex HOT 1
- Incorrect sorting of bibliography HOT 12
- Stopword capitalized after abbreviation HOT 6
- Use citeproc for style development HOT 11
- Support for link/color only the year in the citations HOT 1
- Can I replace the citation key with bibliography? HOT 3
- Author-in-text citations render as superscript HOT 3
- Add support for semantic markup in bibliographies HOT 3
- Disambiguation error HOT 4
- `Undefined Control Sequence \citeproctext` in custom pandoc template HOT 2
- Short DOI prefix in citations HOT 11
- Custom Field in CSLJson silently dropped HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from citeproc.