Style Error: Chicago Author-Date: collapse
CMoS, 16e, 15.29 ("Multiple text references") demands,
"Additional works by the same author(s) are cited by date only, separated by commas except where page numbers are required.
[Examples:]
(Whittaker 1967, 1975; Wiens 1989a, 1989b)
(Wong 1999, 328; 2000, 475; García 1998, 67)"
I suggest adding 'collapse="year"' to <citation ... > in chicago-author-date.csl.
'collapse="year"' works well with both pandoc and Zotero. One problem remains, however: The rule "date only, separated by commas" is followed, but the exception "except where page numbers are required" is not. In the latter case, a semicolon should be used (after "328") where the actual output of both pandoc and Zotero is a comma:
(Wong 1999, 328, 2000, 475; García 1998, 67)
Can this be solved within the existing CSL schema, or is it a schema issue?
"Additional works by the same author(s) are cited by date only, separated by commas except where page numbers are required.
[Examples:]
(Whittaker 1967, 1975; Wiens 1989a, 1989b)
(Wong 1999, 328; 2000, 475; García 1998, 67)"
I suggest adding 'collapse="year"' to <citation ... > in chicago-author-date.csl.
'collapse="year"' works well with both pandoc and Zotero. One problem remains, however: The rule "date only, separated by commas" is followed, but the exception "except where page numbers are required" is not. In the latter case, a semicolon should be used (after "328") where the actual output of both pandoc and Zotero is a comma:
(Wong 1999, 328, 2000, 475; García 1998, 67)
Can this be solved within the existing CSL schema, or is it a schema issue?
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
One option would be to fall back from using any custom delimiter to the delimiter set on cs:layout whenever two neighboring years or year-suffixes are separated by additional content (like a locator). This could be a configurable toggle.
Or we could introduce another delimiter, like after-locator-delimiter.
As to the additional problem with page numbers, either of @Rintze's suggestions sound sensible:
> One option would be to fall back from using any custom delimiter to the delimiter set on cs:layout whenever two neighboring years or year-suffixes are separated by additional content (like a locator). This could be a configurable toggle.
> Or we could introduce another delimiter, like after-locator-delimiter.