Closed dchawisher closed 4 years ago
Thanks for this. We can add a style option to disable suppression. Something like disable-duplicate-year-suppression="us"
, binding the disable to jurisdiction, would allow Canadian cites to render correctly in the same document. Limiting suppression on the basis of date-parts
is probably appropriate, and with the other change, there wouldn't be temptation to use it as a workaround. Would that work?
That would be perfect. Thank you.
This is in the processor master now, and will appear at the next release (which might take some time---now clearing a bunch of interrelated issues for Austria and Germany). code: https://github.com/Juris-M/citeproc-js/commit/f52ac8e7b86cf2b0bb6cf0529ac472e8bdbc39cf test: https://github.com/Juris-M/citeproc-js/commit/6b1c3c8d067f526a402eb092bfc7eb28409a1771 oops-fix: https://github.com/Juris-M/citeproc-js/commit/dc69e7cfdd67b6335775ff1b141708130d843663
In certain circumstances, cireproc-js suppresses the
issued
date field forlegal_case
citations. This happens when all of the following are true:collection-number
field is present.issued
field is displayed withdate-parts="year"
.collection-number
field is the same as the year portion of theissued
field.I understand that this is intentional and that it is necessary to properly render some citation styles. I would still request that the functionality be changed to include a style-level or module-level off-switch, for two reasons.
year-month-day
oryear-month
, but the field in question only has a year, the year will not be suppressed. So it is possible to render a citation like Joe v. Jim, 2020 WL 12345 (N.Y. 2020)—you simply have to tell the style module to render year-month-day but only give it a year.Sorry for the length of this explanation, and thanks for considering it.