I have an issue where author names that do not begin with a capital letter (such as de Broglie, von Neumann, etc.) appear in the references after the author names beginning in capitals, instead of at their first letter regardless of its capitalization.

I am using the MNRAS template: cls and bst.

Here is a minimal example:

\citet{deAuthor}, \citet{Zebra}, \citet{DeCapitalized}

and the refs.bib file has:

@article{deAuthor, author = {de Author, Person}, year = {2015}}
@article{DeCapitalized, author = {De Capitalized, Person}, year = {2016}}
@article{Zebra, author = {Zebra, A.}, year = {2017}}

The reference list shows "De Capitalized, Zebra, de Author" instead of "de Author, De Capitalized, Zebra". Just to be sure I checked the journal's author guidelines but they include nothing to say this is the correct order, and many published papers I checked have it the right way (i.e., "de" with "De" and not at the end).

I originally saw this on Overleaf but I checked on my machine with BibTeX and PdfLaTeX and I get the same result. How do I fix this reordering?

  • It's actually quite common to capitalize the first letter in the "von" component of a person's full if the ordering is "voncomponent surname, givenname(s)". E.g., one writes "De Vries, Casper G." if the name occurs at the very beginning of an entry, but also "Casper G. de Vries". The mnras bibliography style appears to simply adhere to this widespread practice. – Mico Apr 27 '17 at 11:27
  • Possibly, but the BibTeX entries for such papers (generated by ADS) do not include this capitalization, nor have I seen it in any paper's bibliography. Even when such authors cite their own previous work they put their surname prefix uncapitalized. – buzjwa Apr 27 '17 at 11:36
  • I think you've misunderstood my comment. There are *many" typographic conventions. I did certain not claim that the convention implemented by the mnras style is universal or unique. All I said, then, is that saying that the mnras style is somehow wrong is not warranted. – Mico Apr 27 '17 at 11:56
  • It turns out that there is already a github issue on this very point. I've just poked it (no promises...). – Norman Gray Dec 21 '18 at 10:32

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.