On Fri, Dec 29, 2017 at 05:02:20AM +, Steve Litt wrote:
> On Thu, 28 Dec 2017 11:50:27 -0800 (PST)
> Rich Shepard wrote:
>
> > On Thu, 28 Dec 2017, Scott Kostyshak wrote:
> >
> > > Rich, it would be great if you could send MWE for messages like
> > > this. The first step is: remove all text
On Thu, 28 Dec 2017 11:50:27 -0800 (PST)
Rich Shepard wrote:
> On Thu, 28 Dec 2017, Scott Kostyshak wrote:
>
> > Rich, it would be great if you could send MWE for messages like
> > this. The first step is: remove all text and just put "hello". Does
> > that compile? If so, then figure out the sm
On Thu, 28 Dec 2017, Paul A. Rubin wrote:
Looks okay to me. I assume that JabRef is storing that in a .bib file
somewhere. If you want to send me the .bib file, the .tex file and the log
file with the warning, I can take a look (most likely not until tomorrow,
though). I promise not to disclose
On 12/28/2017 06:04 PM, Rich Shepard wrote:
On Thu, 28 Dec 2017, Paul A. Rubin wrote:
I assume you're using bibtex (as opposed to biber or biblatex) to
generate references.
Paul,
Yeah, bibtex. Here's the error message running pdflatex on the .tex
file:
Package natbib Warning: Citation `
On Thu, 28 Dec 2017, Paul A. Rubin wrote:
I assume you're using bibtex (as opposed to biber or biblatex) to generate
references.
Paul,
Yeah, bibtex. Here's the error message running pdflatex on the .tex file:
Package natbib Warning: Citation `Goovaerts1997' on page 58 undefined on input
l
On 12/28/2017 04:04 PM, Rich Shepard wrote:
On Thu, 28 Dec 2017, Paul A. Rubin wrote:
If the glitch is in a BibTeX reference, ...
Paul,
I found the reported warnings, but still get the same compile error
from
lyx. Here's an update:
Running pdflatex on the *.tex file was followed by ru
On Thu, 28 Dec 2017, Paul A. Rubin wrote:
If the glitch is in a BibTeX reference, ...
Paul,
I found the reported warnings, but still get the same compile error from
lyx. Here's an update:
Running pdflatex on the *.tex file was followed by running bibtex on the
*.aux file. It showed 4 war
On Thu, 28 Dec 2017, Paul A. Rubin wrote:
If you're using BibTeX, the BibTeX file could be the culprit. Sometimes
people copy citations (or parts thereof) from non-text sources (e.g., PDF
files) and paste them into a .bib file. They look benign, but there are
character codes (ligatures come to m
On Thu, 28 Dec 2017, Scott Kostyshak wrote:
Rich, it would be great if you could send MWE for messages like this. The
first step is: remove all text and just put "hello". Does that compile? If
so, then figure out the smallest .lyx file that can give the same error.
Scott,
I think that I fou
On 12/28/2017 02:50 PM, Rich Shepard wrote:
On Thu, 28 Dec 2017, Scott Kostyshak wrote:
Rich, it would be great if you could send MWE for messages like this.
The
first step is: remove all text and just put "hello". Does that
compile? If
so, then figure out the smallest .lyx file that can give
On Thu, 28 Dec 2017, Scott Kostyshak wrote:
Rich, it would be great if you could send MWE for messages like this. The
first step is: remove all text and just put "hello". Does that compile? If
so, then figure out the smallest .lyx file that can give the same error.
Scott,
The .lyx file is 8
On Thu, Dec 28, 2017 at 07:22:19PM +, Rich Shepard wrote:
> I've no idea where to look for the source of
> this error and would appreciate a pointer or two.
Rich, it would be great if you could send MWE for messages like this.
The first step is: remove all text and just put "hello". Does that
I've added text to the book and now it chokes at compiling. The reported
problem is with this text: "variables) to describe their objectives and
actions needed to achieve them." and the error window is shown in the
attached screenshot.
There were no problems compiling the document before and
13 matches
Mail list logo
