-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
ISBN Generator output does not follow convention for author names #2343
Comments
So this is a problem of the returned BibTeX of ebook.de?! The only thing we could do is to run a normalization on the returned data. This is one thing you should be able to do manually as well to fix this issue. As you can see the BibTeX key is also not formated as expected. For me, the question here is: |
Responsibility of the fetcher. We have |
@stefan-kolb Ah, good to know, thank you for the hint! If it is possible to detect that the format is not correct, one could offer this as a dialog after having generated the entry, because I did not know that this normalization feature even exists.. |
|
Unfortunately, the above name list is not following the bibtex standard. See http://tex.stackexchange.com/a/36397/9075. Thus it should be fixed in |
Should be fixed in JabRef 3.8 with #2374. |
JabRef 3.7
Archlinux Kernel 4.8.12-2
Java 1.8.0_112 (OpenJDK)
The results of the ISBN Generator are not following the conventions for author names which leads to references that cannot be resolved in LaTeX.
Steps to reproduce:
Result:
David Steinberg, Frank Budinsky, Marcelo Paternostro, Ed Merks
Should be:
Steinberg, David and Budinsky, Frank and Paternostro, Marcelo and Merks, Ed
The result of the request http://www.ebook.de/de/tools/isbn2bibtex?isbn=0321331885 is:
The entry above is just an example. I tested this with several other books having mutliple authors with a similar outcome.
Obviously the JabRef implementation is not the issue but the service that is hardcoded into the application.
The text was updated successfully, but these errors were encountered: