-
-
Notifications
You must be signed in to change notification settings - Fork 287
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
Duplicate "note" is not correctly commented out in biblatex output #3040
Comments
Can you get me a debug log by right-clicking that item and sending the log from the popup menu? |
ACBSRIYI-refs-apse/6.7.248-6 I've modify the entry somewhat but the problem is the same:
|
I cannot reproduce the problem with |
I think I have a fix but without a testcase I can't prevent regressions later |
🤖 this is your friendly neighborhood build bot announcing test build 6.7.248.7247 ("cleanup") This update may name other issues, but the build just dropped here is for you; it just means problems already fixed in other issues have been folded into the work we are doing here. Install in Zotero by downloading test build 6.7.248.7247, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...". |
The test build fixed the problem. Thank you!!! The following is the current biblatex database generated by BBT:
The HTML code |
Yeah I know but I'd prefer to have the actual case in my test suite. The log you sent doesn't have the note that caused the problem so I have no test case to prevent regression. |
Debug log ID
3ZW88UUZ-apse/6.7.248-6
What happened?
I have a note
TEOS-10 homepage is http://www.teos-10.org/index.htm
written by me and attached to an entry. The entry also has a string "OCLC: 724024071" in the
Extra
field, which was inserted there by the Zotero browser plugin.The biblatex output then includes this extra info
Note that there is a linebreak between
</p>
and</div>
. As a result, the piece of text</div>") ignored
is not commented out andbiber
complainsThe text was updated successfully, but these errors were encountered: