Add support of BibLaTeX extended name format

[douglasrizzo]

JabRef version 4.3.1

• I have tested the latest development version from http://builds.jabref.org/master/ and the problem persists

Steps to reproduce the behavior:

1. Have an entry in the database in which the first author name is written using the BibTeX extended name format, for example:

@InProceedings{Hasselt2016,
  author     = {family=Hasselt, given=Hado P., prefix=van useprefix=false and Guez, Arthur and Hessel, Matteo and Mnih, Volodymyr and Silver, David},
  title      = {Learning Values across Many Orders of Magnitude},
  booktitle  = {Advances in Neural Information Processing Systems},
  date       = {2016},
  pages      = {4287--4295},
  url        = {http://papers.nips.cc/paper/6076-learning-values-across-many-orders-of-magnitude},
  urldate    = {2017-06-07}
}

2. In the main table, click the header of the column author/editor to sort entries by author/editor name.

Expected behavior: the example entry should be listed under the letter H (for Hasselt) or maybe V (for the van prefix).

Actual behavior: The example entry is listed first in my database, probably using the "f" letter of the "family" word for sorting.

Additional info: The BibTeX extended name format is somewhat described in section 3.8 of the Biber manual.

[Siedlerchr]

Hi, JabRef and BibTeX don't support semantic annotations of authors, e.g. given or prefix.
JabRef applies a similiar author parsing algorithm as bibtex. So you can just write Hado P van Hasselt and JabRef will figure the name parts automatically.

And also please always test the latest dvelopment version (There's a reason why we put that in the issue description)

http://mirrors.ibiblio.org/CTAN/macros/latex/contrib/biblatex/doc/biblatex.pdf

[tobiasdiez]

@NorwayMaple this might be a good issue for you. In the end it concerns mainly https://github.com/JabRef/jabref/blob/master/src/main/java/org/jabref/model/entry/AuthorListParser.java and does not involve any frontend programming.

[abepolk]

@tobiasdiez I was thinking of working on the issue I mentioned on Gitter relating to multiple instances of JabRef. See the issue there for details.

[douglasrizzo]

@Siedlerchr the problem is not necessarily how JabRef actually parses author names, but that there are some annotations in the "name-level" that are actually useful and can't be directly translated by simply parsing an author's name. In my example, the useprefix annotation alters the behavior of some citation styles. If useprefix=true, the citation style prints "van Hasselt" in citations and references. If its value is false, it prints only "Hasselt".

When working with LaTeX, biblatex allows many of these annotations to be set for an entire document, like so:

\usepackage[useprefix=true]{biblatex}

I've also seen some entries in my bib file keeping "entry-level" configurations in an options field:

@InProceedings{Ree2013,
  author        = {van der Ree, Michiel and Wiering, Marco},
  title         = {Reinforcement learning in the game of Othello: Learning against a fixed opponent and learning from self-play},
  booktitle     = {2013 IEEE Symposium on Adaptive Dynamic Programming and Reinforcement Learning (ADPRL)},
  year          = {2013},
  date          = {2013-04},
  eventtitle    = {2013 IEEE Symposium on Adaptive Dynamic Programming and Reinforcement Learning (ADPRL)},
  note          = {00026},
  publisher     = {IEEE},
  location      = {Singapore, Singapore},
  month         = apr,
  isbn          = {978-1-4673-5925-2},
  pages         = {108--115},
  doi           = {10.1109/adprl.2013.6614996},
  url           = {http://ieeexplore.ieee.org/document/6614996/},
  options       = {useprefix=true}
}

But suppose I have two authors in the same entry, one which would need useprefix=true and the other with useprefix=false in order to have their names printed correctly. JabRef could use the annotations to initially parse a name and strip the annotations afterwards, but these configuration annotations would need to somehow be kept.

Keep in mind that useprefix is not the only annotation that behaves like this. There are others that dictate how each author's initials should be created (by either adding or ignoring dashes, prefixes and suffixes) and so on.