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

Support BibLaTeX's extended name format #73

Open
salim-b opened this issue Mar 8, 2020 · 0 comments
Open

Support BibLaTeX's extended name format #73

salim-b opened this issue Mar 8, 2020 · 0 comments

Comments

@salim-b
Copy link

salim-b commented Mar 8, 2020

It would be cool if RefManageR (i.a. RefManageR::ReadBib()) supported BibLaTeX/Biber's extended name format which allows to explicitly specify the individual parts of names (family, given, prefix, suffix).

Better BibTex for Zotero already supports it and offers an option to use this extended name format during export (disabled by default).

When reading the following entry with the extended name format using RefManageR::ReadBib()

@article{vanDeursen.2010,
  title = {Internet Skills and the Digitial Divide},
  author = {family=Deursen, given=Alexander, prefix=van, useprefix=true and family=Dijk, given=Jan, prefix=van, useprefix=true},
  date = {2010},
  journaltitle = {New Media \& Society},
  volume = {13},
  pages = {893--911},
  number = {6}
}

this error is thrown:

Ignoring entry ‘vanDeursen.2010’ (line11499) because: 
	The name list field author cannot be parsed

Reading in the same entry in the traditional BibTeX name format is fine (the only differences being the lines author = {van Deursen, Alexander and van Dijk, Jan}, and options = {useprefix=true}).


BibLaTeX/Biber's extended name format is documented in chapter 3.8 of Biber's manual and reads:

Extended Name Format

The parsing rules for names are rather archaic and not suited to many international name formats. Biber supports an extended name format which allows explicit specification of the parts of names. This allows the use of custom name parts apart from the four standard BibTeX parts. Extended name formats are supported in all name fields and can be used along with the usual BibTeX name format. Recognition of extended name format can be disabled with the Biber option --noxname in case you do not need the extended format and the auto-detection causes problems with normal name parsing. The separator = which comes between the namepart names and values is customisable with the Biber option --xnamesep. Here is an example:

AUTHOR = {Hans Harman and Simon de Beumont}
AUTHOR = {given=Hans, family=Harman and given=Simon, prefix=de, family=Beumont}

These two name specifications are equivalent but the extended format explicitly names the parts. The supported parts are those specified by the Biblatex data mode constant nameparts, the default value of which is:

\DeclareDatamodelConstant[type=list]{nameparts}{prefix,family,suffix,given}

As with traditional BibTeX name parsing, initials are automatically generated but it is also possible to specify these explicitly:

AUTHOR = {given=Jean, prefix=de la, prefix-i=d, family=Rousse}
AUTHOR = {given={Jean Pierre Simon}, given-i=JPS}

Initials are specified by adding the suffix -i to the namepart name. Compound parts may be protected with braces:

AUTHOR = {given={Jean Pierre}}

If a namepart contains a comma, the whole namepart should be protected with quotes:

AUTHOR = {"family={Robert and Sons, Inc.}"}

Traditional BibTeX name formats and the extended form may be used together:

AUTHOR = {Hans Harman and given=Simon, prefix=de, family=Beumont}

Per-namelist and per-name options may be specified in the extended name format:

AUTHOR = {namelistopt=true and Hans Harman and
          given=Simon, family=Beumont, nameopt=true}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants