-
Notifications
You must be signed in to change notification settings - Fork 6
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
bib2df parsing issues #49
Comments
Thanks @mattwarkentin for the feedback! I used bib2df, as bibtex was orphaned on CRAN and back then it was not clear whether it would ever return. I'll have to think on how to catch this problem. If you have suggestions, please do share them! |
Seeing the active development on the bibtex package (ropensci/bibtex#45), i might switch back to that on the long run. |
Thanks for the quick reply. Yes, perhaps |
This allows users to copy-paste BibTex from (e.g.) Google Scholar ```r drop_name("@Article{rungta2022geographic, title={Geographic Citation Gaps in NLP Research}, author={Rungta, Mukund and Singh, Janvijay and Mohammad, Saif M and Yang, Diyi}, journal={arXiv preprint arXiv:2210.14424}, year={2022} }") ``` In that context, it also deals with nucleic-acid#49 - while we should prob not edit bib-files here, it seems fair to add a workaround for this interactive use until bib2df addresses the issue?
Hi @nucleic-acid,
Cool package!
I was running into a frustrating issue when I tried to play around with it, but it turns out it is caused by
bib2df
. A related issue is found here: ropensci/bib2df#53Unfortunately, Google Scholar provides BibTeX citations without whitespace around the equals sign, by default. So any citation grabbed from Google Scholar fails when parsed by
bib2df
and thus creates incomplete visual citations viadrop_name()
.Just something you might want to know/guard against in this package until it is resolved in that package.
The text was updated successfully, but these errors were encountered: