-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Warn on empty entrykey (bibtexkey) #4440
Comments
I think there is a setting, which enables the Warning of empty bibtexkeys |
There is a warning about the empty key in the integrity check. However, the warning message is not shown in the entry editor. |
Oh, I might have overlooked such an option. I have the Enforce legal characters in BibTeX keys option checked, but that does not help with empty keys as far as I can tell (FWIW I don't quite understand what the option does: the quite dangerous Re the integrity check: I might be missing something obvious. But if I open the file I posted above with JabRef in |
I've been playing around with this issue. Would it be ok to try to help with it? |
Sure, go ahead! If you need any further help or have questions just ask here or in our gitter chat |
* added a warning icon for empty Bibtex keys in entry editor * fixed formatting issue in FieldCheckers.java * modified logic and error message in ValidBibtexKeyCheck.checkValue * Revert "fixed formatting issue in FieldCheckers.java" This reverts commit 9271562. * Revert "modified logic and error message in ValidBibtexKeyCheck.checkValue" This reverts commit bad8856. * changed status message for empty BibTeX keys to one in localization resources * ordered class imports alphabetically in FieldCheckers.java * added entry to CHANGELOG.md for issue #4440 * removed explanation text for issue 4440 fix and updated boolean toggle for empty or null BibTeX keys
Small Enhancement
All
.bib
entries processed by Biber must have a non-emptyentrykey
. Entries without a key, e.g.produce an error along the lines of
and the compilation will abort.
biblatex
with the BibTeX backend will not error on an emptyentrykey
, but the entry can not be cited and will not be added to the bibliography even with\nocite{*}
.Classical BibTeX adds entries without key to the bibliography with
\nocite{*}
, but does not allow to cite them. In any way there can only be one entry with an empty entrykey (after all the key must be unique).Conclusion: Even though empty entry keys are half possible, they don't quite work as expected and I can't imagine any user choosing an empty key on purpose.
Suggestion JabRef already warns the user directly in the editor view with a little icon if the
year
field is not a four-digit integer and if it detects journal abbreviations. It seems like a good idea to also warn the user if they leave the entry key empty.Just to be sure: I tested with JabRef 4.3.1 and did not get an error or a warning about empty keys in the editor view. I also got no report from "Ctrl+F8" on the file
But when I was just playing around with JabRef I saw a message about entrykeys at one point (I can reproduce messages about a key that does not match the automatic pattern, but I could have sworn I also managed to get one about an empty key once, I can't reproduce that one, though), so it seems that some kind of detection is already built-in.
edit: https://tex.stackexchange.com/q/457685/35864 on TeX.SX started this. The OP had an empty entrykey in a JabRef-generated file and was surprised that Biber would report a syntax error.
The text was updated successfully, but these errors were encountered: