-
-
Notifications
You must be signed in to change notification settings - Fork 277
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
[Feature]: export "standard" item type #2543
Comments
I'd rather know what you want the output to look like. The compiled code you are looking at has changed since so it's easier for me to work from a sample. |
Are you exporting to bibtex or biblatex? |
Before I modified it, the entry of this document in the exported .bib file was:
When I complete the above modification, the entry of the document in the exported .bib file is:
Their difference lies in the change of document type mark. |
That's bibtex though. Bibtex doesn't know a |
oh, I see. Thank you! |
Debug log ID
YBFQAFYY-refs-euc
What happened?
A bug happened! I am using BBT in zotero. Today i found that BBT cannot export references of type "standard". I use the software 7-Zip to check zotero-better-bibtex-6.6.79.xpi. I opened the file ./content/workder/zotero.js, and after searching and comparing, I found that the "standard" item was missing in some places. Specifically: 128764 lines, 131569 lines. Refs of type "standard" will be marked as "msic". After supplementing these two omissions, the Refs marked with "standard" can be exported correctly.
The corrected codes in zotero.js are shown as follow:
line 128764 :
types: /* @PURE */ new Set(["article", "book", "bookinbook", "booklet", "collection", "inbook", "incollection", "inproceedings", "inreference", "manual", "misc", "mvbook", "mvcollection", "online", "patent", "periodical", "proceedings", "reference", "report", "set", "suppbook", "suppcollection", "suppperiodical", "thesis", "unpublished", "standard"]),
lines 131568-131570:
report: "techreport",
standard: "standard",
statute: "misc",
The text was updated successfully, but these errors were encountered: