-
-
Notifications
You must be signed in to change notification settings - Fork 276
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
url field is having its special characters escaped in BBT Bibtex #1716
Comments
It looks like you did not upload an debug report. The debug report is important; it gives @retorquere your current BBT settings and a copy of the problematic reference as a test case so he can best replicate your problem. Without it, @retorquere is effectively blind. Debug reports are useful for both bug analysis and enhancement requests; in the case of export enhancements, I need the copy of the references you have in mind. If you did try to submit a debug report, but the ID looked like This request is much more likely than not to apply to you, too, even if you think it unlikely, and even if it does not, there's no harm in sending a debug log that turns out to be unnecessary. @retorquere will more often than not just end up saying "please send a debug log first". Let's just skip over the unnecesary delay this entails. Sending a debug log is very easy:
Once done, you will see a debug ID in red. Please post that debug id in the issue here. Thank you! |
When I compile this:
I get the URL as expected. When I compile this:
I get an error, and no URL is output. So it looks like for bibtex, the escaping is necessary. BTW, if you send a debug log via the steps described in point 1, I get sent the reference in debug log format automatically; my workflow is built around that. This worked though. |
Sorry about the debug stuff. Lesson learned. Thanks a lot |
No worries about the debug log -- I'm happy you sent one. You wouldn't believe how stubborn people can be about sending them. It's one of the primary reasons I built @label-gun, because it would be practically a given people would not send one no matter how I pleaded. WRT the URL -- things are more complicated than I had thought. It is true that
gives me an error, but
compiles just fine. I'll have to think about how to deal with both situations. |
🤖 this is your friendly neighborhood build bot announcing test build 5.2.102.247 ("fixes #1716") Install in Zotero by downloading test build 5.2.102.247, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...". |
Problem solved. It's worked perfectly. |
Cool, thanks for the confirmation. A new release is building. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Exporter used: Better Bibtex
Expected behavior:
Actual behavior:
The error is in the url field. Although the url field is marked as a verbatim field, when exporting using BBT Bibtex, special characters are escaping (in the example "%" is being escaped).
The error only happens in BBT Bibtex, using BBT Biblatex or the standard Zotero Bibtex, everything is fine.
url = {https://medium.com/@eam.avelar/o-que-\%C3\%A9-auc-e-roc-nos-modelos-de-machine-learning-2e2c4112033d}
with%
being scaped.Version of the systems where the error occurs:
Zotero version: 5.0.94
Zotero version: 5.0.95-beta.3 + 4db61b8dc
OS: macOS 11.1
BetterBibtex Debug Json file:
The text was updated successfully, but these errors were encountered: