| I have seen very few fully correct bibliographies written with bibtex in the wild.
Not everything wrong with bibtex is a bug; the big problem is that bibtex is not adapted to its modern usage. A non-comprehensive list of problems: 1. Does anyone run bibtex directly from the command line? No, it's an extra step and the syntax is hard to memorize (should it run on the tex or the bib, and with or without the extension?). Instead, everyone eventually uses some form of script that does "pdflatex; bibtex; pdflatex; pdflatex" or something like this. Nice and slick; unfortunately it means that all warnings get hidden from view. A common mistake (particularly when copypasting) is accidentally having two AUTHOR fields in a bibitem, which causes the second to be ignored. No way you'll notice until you look carefully at the bibliography or read the bibtex log. It doesn't help that many of the warnings are false alarms. 2. Writing bibitems is probably as painless as it could be, but still painful enough that most people have "wandering" bib files that move from project to project. Unfortunately, this creates lots of problems: 2A. A book gets a reedition, or an arXiv preprint gets updated. You just update the reference, right? Wrong, of course, because your old references now lead to the wrong pages, sections, theorems. 2B. There are bibliography styles that print DOI fields but not URLs. There are ones that print URLs but not DOIs. There are some that print both, which is redundant. With a wandering bib file, which ones do you cater to? No way to do right by them all. 2C. With grey literature, a URL is often necessary, but many bibliography styles don't print URLs. So you end up including it in a NOTE field, which of course gets it duplicated in those styles that do print URLs. 3. Too many foot-guns. 3A. Bibtex (or most styles) automatically removes capitalization in titles ("Generalizations of dyck words"). Why? Why??? Yes, you can fix it by putting the {C}apital letters in braces. But why should you? 3B. You cannot use the packages or macros from your tex file in your bib file, as it's a separate file. Of course... but that makes you wonder why it should be a separate file to begin with. 3C. Yes, you heard it right: no package, in particular no unicode support. 3D. Basically every bibtex tutorial tells you to not trust bibitem-generating services, even the most official ones (IEEE, ACM). But no one has the time to do this on their own, and it stands to reason that there should be a common source at least for everything that is published and indexed. We got ORCID and DOI; is this that much harder? |
I’m definitely open to the idea that we should change how we refer to other findings, but EndNote, Zotero, and the like also can’t save you from new editions, overly-strict rules about reference formatting, and bad publisher-provided information.
If you can deviate slightly from a particular reference format, it’s fairly easy to emit either a DOI or a URL (but not both): https://tex.stackexchange.com/questions/154864/biblatex-use-... One of the linked answers even suppresses DOI-like URLs.