Date field passthrough issue after updating to Zotero 2.1
Here is a pretty ugly problem that appears after upgrading to Zoter 2.1. This is a problem in Word documents, so probably to do with the CSL1.0 implementation in the Word plugin.
I suddenly find that a cite that appeared as "Jakobson 1980" now shows up as "Jakobson Autumn" in my document (CMoS, Harvard, MLA, Unified Style Sheet for Linguistics all have this problem). The date field tells me that this record has "Autumn, 1980" in the db, parsed as "y". This is as imported by the JSTOR translator.
Is this intended behaviour? I hope not! I think many people are going to be hit by this problem. Worse, one is not aware of it until one actually stumbles upon a cite that used to look right but now comes out as "Author, Season"!
I suddenly find that a cite that appeared as "Jakobson 1980" now shows up as "Jakobson Autumn" in my document (CMoS, Harvard, MLA, Unified Style Sheet for Linguistics all have this problem). The date field tells me that this record has "Autumn, 1980" in the db, parsed as "y". This is as imported by the JSTOR translator.
Is this intended behaviour? I hope not! I think many people are going to be hit by this problem. Worse, one is not aware of it until one actually stumbles upon a cite that used to look right but now comes out as "Author, Season"!
/ edit, [expletive deleted], it is a problem in the bibliography too! So I get:
Jakobson, Roman. Autumn. Subliminal Verbal Pattering in Poetry. Poetics Today, 2, 127-136.
This is Winword integration 31b1 in Word 2002.
The multilingual version shows the same behavior out of the box, but when run with the citeproc-js date parser (controlled by the hidden preference in the patch discussed here), the citation comes out as "(Smith 2001)" (no [expletive deleted]!).
It looks like this is a bug in the Zotero date parser.