Re: BibTeX issue: journal name not seen by LyX
On Thu, Feb 08, 2018 at 01:10:38AM +, Rich Shepard wrote:
> journaltitle = {Chemosphere},
I know nothing about this, but should this be "journal = " ?
Scott
signature.asc
Description: PGP signature
BibTeX issue: journal name not seen by LyX
There's one citation in my document that's giving me fits. LyX tells me
that the journal name is missing, but it's present in the jabref bibtex
entry:
@Article{Helsel2006,
author = {Helsel, D.R.},
title= {Fabricating data: How substituting values for nondetects can
ruin results, and what can be done about it},
journaltitle = {Chemosphere},
year = {2006},
volume = {65},
pages= {2434--2439},
When I try to preview or compile this document I get an error about the
journal title not being found; when printed anyway, the bibiography entry is
there but missing the journal title. I deleted the jabref entry and
re-entered it but this makes no difference.
Looking at that inserted citation the journal title is not there:
screenshot attached.
Exporting the document using LaTeX/pdflatex does not put a .bst file in
the directory, only the .tex, .aux, and .log files.
I don't know what other information I can provide, but I've tried
everything I could think of and nothing makes sense to me. If jabref exports
the bibtex entry as above (along with all the other references) why might
lyx be refusing to see the journaltitle line for this one reference.
Rich
Re: KOMA-Script classes: old font warnings
Am Mittwoch, den 07.02.2018, 09:01 -0800 schrieb Rich Shepard: >A couple of documents ago I switched the style to authordate4, but > this > issue came up only late yesterday with the 2011 .lyx file. Perhaps > something > I changed in jabref caused it. No, JabRef does not switch your Bib style. You must have done this yourself in LyX (the Bib style is individual to each document). Jürgen > > Best regards, > > Rich signature.asc Description: This is a digitally signed message part
Re: KOMA-Script classes: old font warnings
On Wed, 7 Feb 2018, Jürgen Spitzmüller wrote: Well, it depends on the style file you use (in LyX: "Bibliography Style" in the BibTeX settings dialog). Jürgen, A couple of documents ago I switched the style to authordate4, but this issue came up only late yesterday with the 2011 .lyx file. Perhaps something I changed in jabref caused it. Best regards, Rich
Re: KOMA-Script classes: old font warnings
Am Mittwoch, den 07.02.2018, 08:19 -0800 schrieb Rich Shepard: >I wonder why this appears for only one or two files since I've > been > inserting jabref citations in lyx documents for several years now. Well, it depends on the style file you use (in LyX: "Bibliography Style" in the BibTeX settings dialog). Jürgen signature.asc Description: This is a digitally signed message part
Re: KOMA-Script classes: old font warnings
On Wed, 7 Feb 2018, Michael Berger wrote: Rich, this is indeed annoying and one must wonder why this reappears again and again although one does not at all use such "outdated font commands". Michael, As far as I can recall, this is the first time (perhaps the second time) I've encountered this issue in the many years I've used lyx. Fortunately, there is an easy cure.: In > Document > Class > Custom add this: enabledeprecatedfontcommands Thanks. That does the job. You find this cure if you scroll further down in the Description Window of your Error Message. I certainly missed that, Best regards, Rich
Re: KOMA-Script classes: old font warnings
On Wed, 7 Feb 2018, Jürgen Spitzmüller wrote: They come from the BibTeX style file (*.bst). Jürgen, This explains why I did not see them; there's no .bst file in the document's or jabrefdb.bib directories. I wonder why this appears for only one or two files since I've been inserting jabref citations in lyx documents for several years now. Thanks very much for showing me where the issue originates. Best regards, Rich
Re: KOMA-Script classes: old font warnings
Rich, this is indeed annoying and one must wonder why this reappears
again and again although one does not at all uses such "outdated font
commands".
Fortunately, there is an easy cure.:
In > Document > Class > Custom add this: enabledeprecatedfontcommands
You find this cure if you scroll further down in the Description Window
of your Error Message.
Michael
On 07.02.2018 16:50, Rich Shepard wrote:
I have a LyX document written in 2011 I want to revise. I changed the
document class from Standard article to KOMA article and did some
editing.
When I tried to view the dvips output a warning/error window popped up
(see
attached screenshot) telling me that old font commands, specifically
\sc and
\bf, were replaced years ago with the NFSS2 versions. So I went
looking in
the .lyx file for these font declarations and found none.
Thinking I could use some sections from this document in one I'm
currently
writing (using the KOMA report class), I highlighted two sections in the
older document and pasted them in the new one. Using ^x-p to invoke dvips
output generated the same warnings/errors. After a bit I decided that
I did
not need the new additions and deleted them. Trying to view the dvips
output
still produced the same warning/error box. So does compiling the document
using pdflatex. Cannot find anything relevant in the new document's .lyx
file either so I have no idea how to create a MWE.
Since the warning/error font issue seems to be related to one (of two)
citations inserted from jabref (which has not before occurred), I
looked at
the bibtex information in jabref and don't see anything related to old
fonts:
@Article{FoxD2006,
author = {Fox, D.R.},
title = {Statistical issues in ecological risk assessment},
journaltitle = {Human and Ecological Risk Assessment},
year = {2006},
volume = {12},
pages = {120--129},
abstract = {Ecological risk assessment (ERA) is concerned with
making decisions about the natural environment under uncertainty.
Statistical methodology provides a natural framework for risk
characterization and manipulation with many quantitative ERAs relying
heavily on Neyman-Pearson hypothesis testing and other frequentist
modes of inference. Bayesian statistical methods are becoming
increasingly popular in ERA as they are seen to provide legitimate
ways of incorporating subjective belief or expert opinion in the form
of prior probability distributions. This article explores some of the
concepts, strengths and weaknesses, and difficulties associated with
both paradigms. The main points are illustrated with an example of
setting a risk-based "trigger" level for uranium concentrations in the
Magela Creek catchment of the Northern Territory of Australia.},
journal = {Human and Ecological Risk Assessment},
keywords = {statistics, ecological risk assessment, trigger
values, natural resource management},
}
A clue stick on how to determine what/where this new issue
originates is
needed. Again, I've no idea what to provide as a minimum example of the
problem since I cannot find a specific cause in the .lyx file. However, I
have attached the entire error log and hope that more experienced eyes
will
see what I do not.
TIA,
Rich
Re: KOMA-Script classes: old font warnings
Am Mittwoch, den 07.02.2018, 07:50 -0800 schrieb Rich Shepard: >I have a LyX document written in 2011 I want to revise. I changed > the > document class from Standard article to KOMA article and did some > editing. > When I tried to view the dvips output a warning/error window popped > up (see > attached screenshot) telling me that old font commands, specifically > \sc and > \bf, were replaced years ago with the NFSS2 versions. So I went > looking in > the .lyx file for these font declarations and found none. They come from the BibTeX style file (*.bst). Jürgen signature.asc Description: This is a digitally signed message part
KOMA-Script classes: old font warnings
I have a LyX document written in 2011 I want to revise. I changed the
document class from Standard article to KOMA article and did some editing.
When I tried to view the dvips output a warning/error window popped up (see
attached screenshot) telling me that old font commands, specifically \sc and
\bf, were replaced years ago with the NFSS2 versions. So I went looking in
the .lyx file for these font declarations and found none.
Thinking I could use some sections from this document in one I'm currently
writing (using the KOMA report class), I highlighted two sections in the
older document and pasted them in the new one. Using ^x-p to invoke dvips
output generated the same warnings/errors. After a bit I decided that I did
not need the new additions and deleted them. Trying to view the dvips output
still produced the same warning/error box. So does compiling the document
using pdflatex. Cannot find anything relevant in the new document's .lyx
file either so I have no idea how to create a MWE.
Since the warning/error font issue seems to be related to one (of two)
citations inserted from jabref (which has not before occurred), I looked at
the bibtex information in jabref and don't see anything related to old
fonts:
@Article{FoxD2006,
author = {Fox, D.R.},
title= {Statistical issues in ecological risk assessment},
journaltitle = {Human and Ecological Risk Assessment},
year = {2006},
volume = {12},
pages= {120--129},
abstract = {Ecological risk assessment (ERA) is concerned with making decisions
about the natural environment under uncertainty. Statistical methodology provides a
natural framework for risk characterization and manipulation with many quantitative ERAs
relying heavily on Neyman-Pearson hypothesis testing and other frequentist modes of
inference. Bayesian statistical methods are becoming increasingly popular in ERA as they
are seen to provide legitimate ways of incorporating subjective belief or expert opinion
in the form of prior probability distributions. This article explores some of the
concepts, strengths and weaknesses, and difficulties associated with both paradigms. The
main points are illustrated with an example of setting a risk-based "trigger"
level for uranium concentrations in the Magela Creek catchment of the Northern Territory
of Australia.},
journal = {Human and Ecological Risk Assessment},
keywords = {statistics, ecological risk assessment, trigger values,
natural resource management},
}
A clue stick on how to determine what/where this new issue originates is
needed. Again, I've no idea what to provide as a minimum example of the
problem since I cannot find a specific cause in the .lyx file. However, I
have attached the entire error log and hope that more experienced eyes will
see what I do not.
TIA,
Rich
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017 on Slackware
(SlackBuilds.org)) (preloaded format=latex 2017.11.24) 7 FEB 2018 07:24
entering extended mode
restricted \write18 enabled.
%&-line parsing enabled.
**environmental-chem-stat-anal.tex
(./environmental-chem-stat-anal.tex
LaTeX2e <2017-04-15>
Babel <3.15> and hyphenation patterns for 84 language(s) loaded.
(/usr/share/texmf-dist/tex/latex/koma-script/scrreprt.cls
Document Class: scrreprt 2017/09/07 v3.24 KOMA-Script document class (report)
(/usr/share/texmf-dist/tex/latex/koma-script/scrkbase.sty
Package: scrkbase 2017/09/07 v3.24 KOMA-Script package (KOMA-Script-dependent b
asics and keyval usage)
(/usr/share/texmf-dist/tex/latex/koma-script/scrbase.sty
Package: scrbase 2017/09/07 v3.24 KOMA-Script package (KOMA-Script-independent
basics and keyval usage)
(/usr/share/texmf-dist/tex/latex/graphics/keyval.sty
Package: keyval 2014/10/28 v1.15 key=value parser (DPC)
\KV@toks@=\toks14
) (/usr/share/texmf-dist/tex/latex/koma-script/scrlfile.sty
Package: scrlfile 2017/09/07 v3.24 KOMA-Script package (loading files)
))) (/usr/share/texmf-dist/tex/latex/koma-script/tocbasic.sty
Package: tocbasic 2017/09/07 v3.24 KOMA-Script package (handling toc-files)
\scr@dte@tocline@numberwidth=\skip41
\scr@dte@tocline@numbox=\box26
)
Package tocbasic Info: omitting babel extension for `toc'
(tocbasic) because of feature `nobabel' available
(tocbasic) for `toc' on input line 135.
Package tocbasic Info: omitting babel extension for `lof'
(tocbasic) because of feature `nobabel' available
(tocbasic) for `lof' on input line 137.
Package tocbasic Info: omitting babel extension for `lot'
(tocbasic) because of feature `nobabel' available
(tocbasic) for `lot' on input line 138.
Package tocbasic Info: defining new hook before heading of `' on input line 162
7.
Class scrreprt Info: File `scrsize11pt.clo' used instead of
(scrreprt) file `scrsize11.clo' to setup font sizes on input line 229
3.
(/usr/share/texmf-dist/tex/latex/koma-script/scrsize11pt.clo
File:
