On 10/15/21 12:34 PM, Jürgen Spitzmüller wrote:
Here's an MWE and the associated .bib file. Since I installed biber, I no longer fail to generate a bibliography under any scenario, but I can still reproduce behavior that I think is a bug. This is with LyX 2.3.6.1 on Linux Mint 20.2 using TeXLive 2019. I'm using the PDF (pdflatex) output format throughout.Am Freitag, dem 15.10.2021 um 11:51 -0400 schrieb Paul A. Rubin:Over on the user list, there's a lengthy thread (actually set of threads) triggered by user Rich Shepard trying to compile a report whose bibliography stubbornly refused to appear. Rich was using biblatex. After copies trial and error, Rich got the report to work, but with no explanation why.I was beating on a copy of it (which I am not at liberty to share) and discovered that if made any non-fatal change to the preamble, the bibliography would show up. In particular, just adding \usepackage{} (with the argument deliberately empty) to the preamble in LyX coaxed the bibliography to show up. Comparing the .tex files that LyX exported with and without the \usepackage{} command, I discovered two changes. One of course was the inclusion of \usepackage{}. The other was that \usepackage[style=authoryear]{biblatex} in the original document morphed into \usepackage[style=authoryear,backend=bibtex8]{biblatex} in the modified document. So I went to the original document and, in the bibliography settings, changed the processor option from default to bibtex8, and sure enough the original compiled correctly. I'm not sure if this is a bug or something the user is responsible for knowing (it was news to me, but I never use biblatex). So I'm reporting it here to let wiser minds decide.Undecidable without a MWE. Jürgen
1. View the document (which compiles correctly), then run 'grep
biblatex dev_mwe.tex' in the LyX buffer directory. The relevant
output line is "\usepackage[style=authoryear]{biblatex}".
2. Make an arbitrary text change in the document body (anywhere), to
force LyX to recompile. Repeat the previous step. The key line in
the .tex file is unchanged.
3. In Document > Settings... > LaTeX Preamble, add a space at the end
of the preamble and repeat the first step. The line in the .tex file
changes to "\usepackage[style=authoryear,backend=bibtex8]{biblatex}"
(i.e., the "backend" setting is added).
This also happens if I edit the text in the \lehead{}, \rohead{},
\refoot{} or \lofoot{} commands, or if I insert \usepackage{} in the
preamble, or basically if I make any non-fatal change to the preamble.
It makes no sense to me that any of those changes would affect bibliography processing.
Paul 1.
dev_mwe.lyx
Description: application/lyx
% Encoding: UTF-8
@comment{x-kbibtex-encoding=utf-8}
@Article{VanDoornik2019,
author = {Van Doornik, D.M. and Kuligowski, D.R. and Morgan, C.A. and Burke, B.J. and Seamons, T.R.},
journal = {Fishery Bulliten},
title = {Insights, from genetic analyses, into stock-specific distribution of juvenile steelhead (Oncorhynchusmykiss) from the Columbia River during early marine migration},
year = {2019},
doi = {10.7755/FB.117.1-2.11},
pages = {97--106},
volume = {117},
abstract = {For anadromous Pacific salmon (Oncorhynchus sp.), ocean conditions during their initial entry into the marine environment can greatly affect their survival. Different life history types or stocks may experience different conditions during their marine entry because routes of early marine migration can differ among types or stocks. Steelhead (O. mykiss) from the For anadroumous Pacific salmon (Oncohrynchus sp.) ocean salmon (Oncorhynchus sp.), ocean conditions during their initial entry into the marine environment can greatly affect their survival. Different life history types or stocks may experience different conditions during their marine entry because routes of early marine migration can differ among types or stocks. Steelhead (O. mykiss) from the Columbia River are believed to migrate offshore quickly once they enter the ocean, but little is known about whether life history or stock-specific differences in early marine migration exist. We assembled a baseline of steelhead genetic data that allowed us to estimate the genetic stock of origin for juvenile steelhead that had been caught off the coasts of Washington and Oregon in May, shortly after their out-migration from freshwater. We found differences in the average locations of the various genetic stock groups of the Columbia River, dissimilarities that were most likely due to differences in the timing of the marine entry of juveniles. We also observed considerable variation among years in the average location where we caught steelhead and in the number of steelhead caught, results indicating that freshwater or marine conditions can influence the behavior or survival of steelhead.},
keywords = {fish, Columbia River, rivers, steelhead, trout, distribution, juvenile, out-migration},
}
-- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
