So there’s a discussion thread on this Zotero ticket about dates and CSL:
I’d like to move it here to resolve it on the CSL end, with examples.
For sake of simplicity, let’s take two cases:
a. non-month dates: “2003, April/May” or “2005, Fall”
b. approximate dates: “c1034”
From the CSL perspective, I’d expect that if a processor sees …
… it will print those dates.
I guess right now Zotero would strip “c” and “Fall”, based in part on
the position that users will put all kinds of unexpected crap in that field.
So the question is, do we need to care about this here?
It seems to me that answer is probably yes, if the presentation varies
by style and/or language. At minimum, the locales files need terms like
"cerca" and (perhaps) the seasons, as well as “no-date” (if it’s not
already there). That way we leave it to processors to know what to do
with these sorts of dates, and they can choose to do nothing.
But I’m not sure whether we need more, and I’m not sure whether we need
the is-date attribute (which may cause unnecessary confusion for no
clear benefit). E.g. the bottom-line seems to me:
Zotero ought to be less restrictive on passing through dates, and
maybe make date parsing smarter over time to account for these cases,
in CSL, we add the terms noted above, and consider again the
practical use case that “is-date” solves. If we can’t find one, we