> I use bibtex and that's the way both JabRef and LyX are configured. > Yes, so does version 3.8.2 that I use and none of the 'quality' checks do anything.
The Check Integrity function I use is in JabRef 4.1 (the latest). I'd suggest making sure your bibtex file is 100% bibtex as follows: 1. In JabRef, create a new "bibtex" library. 2. Copy all the entries from the existing "biblatex" library and paste them in the library created above. 3. Run "Quality > Check Integrity" and resolve any "biblatex field only" issues. 4. Save the library as the converted "bibtex" library. Cheers, C. Fuhrman On Thu, Feb 8, 2018 at 10:52 AM, Rich Shepard <[email protected]> wrote: > On Thu, 8 Feb 2018, Cris Fuhrman wrote: > > If your JabRef format is biblatex, are you using LyX appropriately? >> https://wiki.lyx.org/BibTeX/Biblatex >> > > Chris, > > No. I use bibtex and that's the way both JabRef and LyX are configured. > > Otherwise, make sure you've updated to the latest Jabref. >> > > I cannot do this because it requires openjfx and that's available for > only 64-bit processors. My desktop has a 32-bit CPU and this issue has come > up only in this document and with references (now 2) from only a single > author. > > It has some tools to validate the bib(la)tex files (Menu Quality > Check >> Integrity, and Menu Quality > Cleanup entries > Convert to biblatex), etc. >> > > Yes, so does version 3.8.2 that I use and none of the 'quality' checks do > anything. > > But beware of the many warnings about small things like non-standard >> author formatting which doesn't matter (the integrity check can produce a >> lot of noise). I had a problem once with a badly encoded accented >> character in the .bib file that caused LyX to just not finish; it took me >> hours to find it (before I knew that Jabref had those tools). >> > > I've checked each journal title field for unprintable characters and > re-written them but nothing makes a difference. > > Rich >
