We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
You can reproduce the problem with doi:10.1145/3589263
BibTeX generated by crossref.org has a protected term in the journal field: {ACM}
{ACM}
$ curl http://api.crossref.org/works/10.1145/3589263/transform/application/x-bibtex
@article{Kuschewski_2023, ... journal = {Proceedings of the {ACM} on Management of Data} }
Because of that, the regular expression to replace the journal field with the abbreviated name fails: https://github.com/bibcure/doi2bib/blob/master/doi2bib/crossref.py#L91
In effect, the BibTeX produced by doi2bib has this malformed line:
@article{Kuschewski_2023, ... journal = {Proc. ACM Manag. Data} on Management of Data} }
In the end, bibtexparser recognizes the whole section as a comment and not an @article
bibtexparser
@article
The text was updated successfully, but these errors were encountered:
I can now see that this problem is fixed by this PR from 2021: #10
Can you please merge it?
Sorry, something went wrong.
No branches or pull requests
You can reproduce the problem with doi:10.1145/3589263
BibTeX generated by crossref.org has a protected term in the journal field:
{ACM}
Because of that, the regular expression to replace the journal field with the abbreviated name fails: https://github.com/bibcure/doi2bib/blob/master/doi2bib/crossref.py#L91
In effect, the BibTeX produced by doi2bib has this malformed line:
In the end,
bibtexparser
recognizes the whole section as a comment and not an@article
The text was updated successfully, but these errors were encountered: