-
-
Notifications
You must be signed in to change notification settings - Fork 294
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 date field in extra #2658
Comments
Addenum: After further testing, it seems that |
Sorry for the delay. Looking into it now. |
The citation key isn't strictly mine BTW, the Zotero bib(la)tex exporters use it too. How are you testing this? I have tried exporting to CSL-JSON (which uses the same transformation) and there the extra field is just dumped into the |
I suspect it may be a citeproc-js issue. As you say, the note field is exported properly. Pandoc also processes the exported items without issues, the visual editor as well. |
Easy to test whether it's BBT -- disable BBT, restart Zotero, and test again. If that still fails, it's unequivocally Zotero, not BBT. If it is BBT, I can look into it further. I'm less familiar with the citeproc part of Zotero. |
Ok – it's not BBT. Same thing happens without BBT. |
Closing here. |
Debug log ID
HQ8N6ANL-refs-euc/6.7.120-6
What happened?
Depending on where
Citation Key
is inExtra
, a directly following date field (maybe onlyevent-date
) is not available to citeproc-js. With the three items from the debug log and the minimal style below, I'm getting the following results:Citation Key
directly aboveEvent date
-> "match" ->Event Date
not usedCitation Key
last inExtra
-> "10. Mai 2001match" -> as expectedCitation Key
first inExtra
-> "10. Mai 2001match" -> as expectedI'm not sure whether this has something to do with Zotero BBT. (I actually doubt it, but I thought I'd better ask since this it involves the
Citation Key
field.)The text was updated successfully, but these errors were encountered: