-
Notifications
You must be signed in to change notification settings - Fork 73
Various name fixes, in particular regarding von-prefix (prelast) & lineage (Jr./Sr./I/II/III/IV/V) #260
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 84a1d1b.
Also some other changes, as some authors also fixed their name on ePrint online, but this was not in cryptobib.
Let LaTeX handle the von prefices, and hope that the .bst file is sorting only by lastname.
Compare these two: - https://orcid.org/0000-0001-7568-8071 - https://www.semanticscholar.org/author/Lloren%C3%A7-Huguet-i-Rotger/1777751 Somehow go for the one from seminatic scholar.
In many cases, you can just remove the braces. Make sure your .bst file sorts by last name, excluding von prefix!
This makes sure that lineages such as II, III, IV are parsed correctly by bibtex! See e.g. Section 11 "The author field" from the bibtex tamethebeast manual.
There are also some names that do not have capitalization, but those occur less frequent than these names, which are clearly inconsistent with the usual way these names are written.
The scripts I used are found in https://github.com/ludopulles/cryptobib_tools/ . In particular the files: Note that to use the "Person" object from mybibtex I modified the cryptobib/lib repo to specify the name output format. |
This was referenced Oct 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request contains multiple changes:
van / van de / de la / von / d'
but notVan / Van de / O'
) was sometimes incorrectly seen as part of the last name, which caused the abbreviation (if using e.g. alpha.bst) to be incorrect like[van ] / [de ]
. As explained in rationale behind some particle names #107 (comment), by using a 'good' .bst-file in your LaTeX file that sorts on last name not including prefix, alphabetic sorting happens as expected. Even with alpha.bst you have abbreviations like[DvW21]
already which is as expected.Lo{\"i}c {van Oldeneel tot Oldenzeel
" to "Lo{\"i}c van {Oldeneel tot Oldenzeel}
" because without the {}-braces, Bibtex thinks "van Oldeneel tot" is the von-prefix (according to the TameTheBeast manual) which it isn't.William E. Skeith III
used to be wrong. I forced an encoding ofvon Last, Jr., First
when a lineage appears, to make sure it's parsed correctly.Gilles Van Assche
" to "Gilles {Van Assche}
".Alfredo De Santis
" to "Alfredo {De Santis}
" (similar for "Ivan {De Oliveira Nunes}
").Youssef El Housni
" to "Youssef {El Housni}
".Frank Y.C. Lu
" to "Frank Y. C. Lu
".I used a script to more or less automate these changes. I can make a PR for these scripts in
db_tools
and thelib
(for changes to Person class) repositories if wanted. I believe that the import scriptdb_import/import.py
needs to be revised to do these names good in the future.Note: this does not update the ePrint labels, also because there was an open pull request #252 . Once this Pull Request is done, I have a fix for all the >6 letter labels and outdated labels, which is here: https://github.com/ludopulles/crypto_db/tree/fix-252
I'll create a PR for that, once/if this is merged.
Closes: #107