Skip to content
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

import bug for BIBTEX multiple keywords tag #483

Closed
g10996694 opened this issue Dec 7, 2015 · 5 comments
Closed

import bug for BIBTEX multiple keywords tag #483

g10996694 opened this issue Dec 7, 2015 · 5 comments

Comments

@g10996694
Copy link

In the bibtex exported from sciencedirect, there are often multiple keywords tags. In fact, every tag contains one keyword.
But jabref takes only the first one, the rest are ignored.
Perhaps parsing loop would help to load all keywords ?

@simonharrer
Copy link
Contributor

Hm, hard to say if this is really a bug or a feature. The problem here is that sciencedirect produces a wrong bibtex format.

@g10996694
Copy link
Author

@simonharrer
Yes, the bibtex format export from ScienceDirect does not respect the rules of BIBTEX.
That's why I use generally the RIS export instead of BIBTEX export.
Just find this problem, it's you to decide :)

@simonharrer
Copy link
Contributor

Probably something for the JabRef developers to discuss. :)

@tobiasdiez
Copy link
Member

Something similar is already done for the author and editor fields.
To cite the BibtexParser:

                // The following hack enables the parser to deal with multiple
                // author or
                // editor lines, stringing them together instead of getting just
                // one of them.
                // Multiple author or editor lines are not allowed by the bibtex
                // format, but
                // at least one online database exports bibtex like that, making
                // it inconvenient
                // for users if JabRef didn't accept it.
                if ("author".equals(key) || "editor".equals(key)) {
                    entry.setField(key, entry.getField(key) + " and " + content);
                }

@lenhard
Copy link
Member

lenhard commented Jan 26, 2016

This is now fixed in master with e1fcdd3

@lenhard lenhard closed this as completed Jan 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants