Check integrity: Support for BibTeX .blg files

[koppor]

When using pdflatex and bibtex on following LNCS class, one gets errors

\documentclass[runningheads,a4paper,english]{llncs}[2022/01/12]
\bibliographystyle{splncs04}
\begin{document}
\title{Paper Title}
\author{Firstname Lastname \and Firstname Lastname}
\institute{Institute}
\maketitle
\begin{abstract}
...
\end{abstract}
\section{Introduction}
...
\section{Related Work}
There are multiple systematic literature reviews (e.g., \cite{Tan_2021} and \cite{Scholey_2013}) ...
\bibliography{Chocolate}
\end{document}

(The .bib file used is https://github.com/JabRef/jabref/blob/7d480508632b4619cb662d4b9f5a1078990da827/src/test/resources/testbib/Chocolate.bib#L1).

The style file: splncs04.bst
Database file #1: Chocolate.bib
Warning--empty journal in Scholey_2013
Warning--empty year in Scholey_2013
Warning--empty journal in Tan_2021
Warning--empty year in Tan_2021
(There were 4 warnings)

JabRef should be able to present these errors.

JabRef already has an integrity check:

It should be possible to handle the bibtex warnings and errors.

Idea: Two tabs: "Internal" and "BibTeX"

• [ ] At the bibtex tab, the user selects a .blg file. (filename field + browse button)
• [ ] As default value, the current library name is used (.bib exchanged with .blg)
• [ ] The dialog remembers the file per library (in case not the default value is used). The setting is stored in the JabRef preferences (not in the library itself). Changing the file to the default value removes the preference
• [ ] Parse the .blg file and show the warnings as messages in the dialog (this is a new class in logic; please also add test cases for it)

[Allan541a]

Hello Kopper, I have studied Java for a year and am very interested in this issue. Can I work on it?

[github-actions[bot]]

Welcome to the vibrant world of open-source development with JabRef!

Newcomers, we're excited to have you on board. Start by exploring our Contributing guidelines, and don't forget to check out our workspace setup guidelines to get started smoothly.

In case you encounter failing tests during development, please check our developer FAQs!

Having any questions or issues? Feel free to ask here on GitHub. Need help setting up your local workspace? Join the conversation on JabRef's Gitter chat. And don't hesitate to open a (draft) pull request early on to show the direction it is heading towards. This way, you will receive valuable feedback.

⚠ Note that this issue will become unassigned if it isn't closed within 30 days.

🔧 A maintainer can also add the Pinned label to prevent it from being unassigned automatically.

Happy coding! 🚀