-
-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Citation Key blocks following fields in note #231
Comments
I don't see |
You're right of course. The But: So:
Any ideas? |
This might be some leftover behavior from creating alignment with BetterBibTeX? @retorquere |
I haven't been able to find anything. Not in citeproc-js, not in the Zotero sources. It's in the translators, but I don't think these are involved. |
Okay, I think I've found it. (First off, when exporting to CSL-JSON the Citation Key field is (re)moved, but this is not the case when generating CSL-JSON for citeproc-js). Zotero transforms "Citation Key" to "citation-key", but this field is not recognized as a CSL-JSON field, and the transformation is canceled (code). "Citation Key" is not a valid variable name (docs, code). Citeproc only parses the note contents up to the first line that does not contain a note field, with the exception that the first line can contain anything:
|
Depending on whether the Citation Key should be available to citeproc or not, the field should either be mapped correctly to |
|
Would zotero/utilities#29 work? |
I think so (and more broadly we need to add the other new variables in CSL 1.0.2 to that list) |
I'll work on it. |
Thanks--I noticed that that needed to be updated a week or so ago and haven't found time to track down exactly where |
I've added them. It might also be useful to move non-CSL fields to the bottom of the field list (to avoid this confusing behavior for typos etc.) but I can imagine that that could cause other issues. |
Thanks. |
Depending on where
citation-key
is innote
, later fields may not be recognized byciteproc-js
. See retorquere/zotero-better-bibtex#2658 (I first thought it might be a BBT issue, but apparently it is not.)With the three items and the minimal style below, I'm getting the following results:
Or is this a problem with how Zotero hands the data over to citeproc-js rather than a citeproc-js issue proper?
The text was updated successfully, but these errors were encountered: